Difference between revisions of "Available Permissions"
From LongJump Support Wiki
imported>Aeric m (Text replace - 'Setup > ' to 'Settings > ') |
imported>Aeric |
||
Line 16: | Line 16: | ||
===Access Permission to Records Owned by Others Within the Team=== | ===Access Permission to Records Owned by Others Within the Team=== | ||
Define permission rights to Update, Delete or View Records owned by Team Members. | Define permission rights to Update, Delete or View Records owned by Team Members. | ||
===Record Access Permissions=== | ===Record Access Permissions=== | ||
Define permission rights to Create or Delete Records in Objects. | Define permission rights to Create or Delete Records in Objects. | ||
===Web Tabs=== | ===Web Tabs=== | ||
Define permission rights to View Web Tabs. | Define permission rights to View Web Tabs. | ||
===Administrative Permissions=== | ===Administrative Permissions=== | ||
{{:Administrative Permissions}} | {{:Administrative Permissions}} |
Revision as of 18:43, 29 July 2011
- Note: Before changing permission rights in a role, see these articles for information about how roles affect data access in the platform
To edit individual permissions:
- Click Settings > Administration > Roles > {role}
- Click the [Edit] button
- Click the Globally Manage Permissions tab
- Click the Yes radio button for each permission you want to specify individually
- Click the Individually Manage Permissions tab and set the permissions as needed
- Individual Access Example
The options available in this page are determined by the Role of the User. The images shown here are for example only, and indicate typical access permission controls.
Access Permission to Records Owned by Others Within the Team
Define permission rights to Update, Delete or View Records owned by Team Members.
Record Access Permissions
Define permission rights to Create or Delete Records in Objects.
Web Tabs
Define permission rights to View Web Tabs.
Administrative Permissions
Administrative Permissions are assigned in an Access Profile. They allow a user to customize selected aspects of the platform. (Data Access Permissions, in contrast, determine what objects, records, and fields a user can see by virtue of their role and team memberships.)
Tip: Users given Administrative Permissions should have the following skills:
- Familiarity with the platform and your organization's business processes
- Good understanding of the Application Design Guide
- Excellent understanding of the area(s) they will be modifying
- User and Ownership Controls
- User Management - Create and manage users and teams
- Access Control - Manage roles and password policies
- Change Ownership of my Team’s Records
- Change Ownership of Self Owned Records
- Manage Personal Setup
- Reporting Controls
- CRM Features
- Data Management Controls
- Application Controls
- Customize Objects
- Manage Applications - Add/Update/Delete platform applications
- Manage Packages
- Manage Translation Workbench
- Development Controls
- Use Development Features - Work with classes, pages, sites, and other development features
- Manage Debug Log
- Manage Sandboxes (Only appears if sandboxes are enabled)
- Account Controls
- Manage Company Capabilities
- Proxy Login Access
- Proxy Login Configuration
- Support Cases - View and modify support cases filed by others
- Administer Versioning (Only appears if versioning is enabled)