|
|
Line 1: |
Line 1: |
− | [[Role]] security is based on a [[Role|role]] that you associate with the [[User|user]]. With this scheme, you first create one or more [[Role|roles]], and then associate each [[User|user]] with one or more of those roles.
| + | #REDIRECT [[Roles and Security Settings#Overview]] |
− | | |
− | By setting a default [[User|user]] [[Role|role]] in your [[Personal Settings|personal settings]], the system will always assume that you are adding someone using a specific [[Role|role]] when you add a new person to the system.
| |
− | | |
− | <u>'''Advantages'''</u>
| |
− | | |
− | There are three advantages to [[Role|role]]-based security:
| |
− | | |
− | * You can make individuals, regardless of their organisation, members of a [[Role|role]] and give them access to a resource.
| |
− | * When you move the [[User|user]] to another organisation, it does not affect their permission to access a resource.
| |
− | * Associating the [[Role|role]] with the resource is less time consuming if the alternative is to associate the resource to many organisations.
| |
− | | |
− | <u>'''Disadvantages'''</u>
| |
− | | |
− | * You must create the [[Role|roles]] and remember to set the appropriate roles when you create a new [[User|user]].
| |
− | * If you upload new [[User|users]], you must choose the correct [[Role|roles]] in the upload wizard; however, you will be prompted.
| |
− | | |
− | This security scheme should be used when the relationships between [[User|users]] and the resources are more complex and you need to provide access to resources independent of any organisational structure.
| |
− | | |
− | ==See Also==
| |
− | * [[The Key Control Element – Roles]]
| |
− | * [[Manager Permissions]]
| |
− | * [[Roles and Security Settings]]
| |
− | * [[:Category:Security]]
| |
− | * [[Security Settings]]
| |
− | | |
− | [[Category:Roles]][[Category:Security]]
| |