Difference between revisions of "Working with Roles"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
(21 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Application users generally fall into categories, or ''roles''. A person in a given role needs permissions to work with some kinds of data, but typically doesn't need to work with other kinds data (or even see it). | |||
It is common for new roles to be added over time, and for | It is common for new roles to be added over time, and for existing roles to evolve as the organization grows and business procedures are refined. | ||
{{ | {{PermissionRef|Access Control|manage user roles.}} | ||
===Add or Edit a Role=== | ===Add or Edit a Role=== | ||
To | To add or edit a Role: | ||
#Click ''' | #Click '''[[File:GearIcon.png]] > Customization > Application Roles'''<br>The roles defined for the current application are listed. | ||
#Click the '''[New Role]''' button to add a role; | #Click the '''[New Role]''' button to add a role; | ||
#Optionally, click an existing role to edit the role | #Optionally, click an existing role to edit the role | ||
#Specify the [[#Role Settings|Role Settings]] (described below) | #Specify the [[#Role Settings|Role Settings]] (described below) | ||
#Click '''[Save]''' | #Click '''[Save]''' | ||
::'''Note:'''<br>The [[System Administrator]] role comes with the platform. | |||
===Clone a Role=== | ===Clone a Role=== | ||
You can clone a role in order to save time in creating a new role that has similar settings. | You can clone a role in order to save time in creating a new role that has similar settings. | ||
To Clone a Role: | To Clone a Role: | ||
#Click ''' | #Click '''[[File:GearIcon.png]] > Customization > Application Roles''' | ||
#Click the name of the role you want to clone. The detail page for that role opens. | #Click the name of the role you want to clone. The detail page for that role opens. | ||
#Click the '''[Clone]''' button.<br>The Add Role page opens, displaying the settings from the Role you cloned. | #Click the '''[Clone]''' button.<br>The Add Role page opens, displaying the settings from the Role you cloned. | ||
Line 31: | Line 27: | ||
===Delete a Role=== | ===Delete a Role=== | ||
To Delete a Role: | To Delete a Role: | ||
#Click ''' | #Click '''[[File:GearIcon.png]] > Customization > Application Roles''' | ||
#Click the name of the role you want to delete; the detail page for that role opens | #Click the name of the role you want to delete; the detail page for that role opens | ||
#Click the '''[Delete]''' button at the top of the page.<br>A confirmation dialog appears. | #Click the '''[Delete]''' button at the top of the page.<br>A confirmation dialog appears. | ||
#Click '''[OK]''' to delete the role. | #Click '''[OK]''' to delete the role. | ||
== | ===Assign Roles to Users and Groups=== | ||
In the [[Application Access]] settings, an administrator specifies which applications a user or group can access, and which Role(s) they assume in those applications. | |||
;Considerations: | |||
:* If a user or group is assigned multiple roles, they have the privileges defined in all of them. (Their set of privileges is the sum of the privileges specified in the assigned roles.) | |||
== | ==Role Settings== | ||
{{: | {{:Role Settings}} |
Latest revision as of 19:24, 9 October 2015
Application users generally fall into categories, or roles. A person in a given role needs permissions to work with some kinds of data, but typically doesn't need to work with other kinds data (or even see it).
It is common for new roles to be added over time, and for existing roles to evolve as the organization grows and business procedures are refined.
Users that have the Access Control permission can manage user roles..
Add or Edit a Role
To add or edit a Role:
- Click > Customization > Application Roles
The roles defined for the current application are listed. - Click the [New Role] button to add a role;
- Optionally, click an existing role to edit the role
- Specify the Role Settings (described below)
- Click [Save]
- Note:
The System Administrator role comes with the platform.
- Note:
Clone a Role
You can clone a role in order to save time in creating a new role that has similar settings.
To Clone a Role:
- Click > Customization > Application Roles
- Click the name of the role you want to clone. The detail page for that role opens.
- Click the [Clone] button.
The Add Role page opens, displaying the settings from the Role you cloned. - Specify the Role Settings (described below)
- Click [Save]
Delete a Role
To Delete a Role:
- Click > Customization > Application Roles
- Click the name of the role you want to delete; the detail page for that role opens
- Click the [Delete] button at the top of the page.
A confirmation dialog appears. - Click [OK] to delete the role.
Assign Roles to Users and Groups
In the Application Access settings, an administrator specifies which applications a user or group can access, and which Role(s) they assume in those applications.
- Considerations
-
- If a user or group is assigned multiple roles, they have the privileges defined in all of them. (Their set of privileges is the sum of the privileges specified in the assigned roles.)
Role Settings
Role Information
- Name
- The name of the role as it will appear in the platform
- Description
- Text that describes this role and its settings (permissions)
Role Permissions
These are the permissions that can be specified for a role:
- Record Access Permissions
- For each object, specify the ability to Create, and Delete records.
- If Record Level Visibility is enabled for an object, specify the ability to Control Visibility.
- (In general, the ability to access an object implies the ability to view any of the records it contains. However, if Record Level Visibility is enabled, a role can also specify the ability to set visibility criteria for individual records, in order to restrict visibility of that record to a designated audience.)
- Access to Records Owned by Others Within the Team
- Specify the ability to Update, Delete, and View records contained in a each object.
(These permissions apply to records owned by a different member of the team.)