|
|
| Line 1: |
Line 1: |
| − | Organisation security is based on the person's “organisation” in the overall [[Hierarchy|hierarchy]].
| + | #REDIRECT [[Organization hierarchy#Organization Based Security]] |
| − | * You permission an “organisation” to access a resource and everyone in that organisation can access that resource.
| |
| − | * When you add new people to this organisation they will automatically gain access to the resource.
| |
| − | | |
| − | ==Organisation Security – Advantages==
| |
| − | | |
| − | This scheme is advantageous when there are people in a specific organisation that need access to a resource.
| |
| − | | |
| − | When you create a [[User|user]] in that organisation you don’t have to set any specific permission for the [[User|user]] to access the resource, as the [[User|user]] will “inherit” access by being associated with the organisation.
| |
| − | | |
| − | ==Organisation Security – Disadvantages==
| |
| − | | |
| − | There are disadvantages to organisation security.
| |
| − | * Organisation security does not allow you to give individual [[User|users]] from different organisations access to the resource.
| |
| − | * You must associate each organisation with the resource. Giving multiple organisations access to the resource can be time consuming.
| |
| − | * If you “move” the [[User|user]] to another “organisation”, then they will automatically lose access to resources associated with their previous organisation.
| |
| − | This scheme is worthwhile for small, less complex, access scenarios that are organisation orientated.
| |
| − | | |
| − | [[Category:Security]][[Category:Roles]][[Category:System Management]]
| |
