Difference between revisions of "Role Permissions"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric m (moved Available Permissions to Role Permissions) |
||
| (22 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
These are the permissions that can be specified for a role: | |||
:: | :'''Record Access Permissions'''<br> | ||
: | :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'''<br> | |||
:{{:Access to Records Owned by Others Within the Team}} | |||
Latest revision as of 23:04, 8 September 2015
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.)