The following table shows various non-administrator user group permission access to services and its subservices and which services and subservices the user group sees.
The Example column uses the following service names: A, B, and C with each service having the subservice D.
|
User Group Service Permission |
User Group Subservice Permission |
Example |
User Group Sees* |
Notes |
|---|---|---|---|---|
|
Not set |
Not set |
Access permissions are not set for services A, B, C, or subservice D |
No services or subservices |
|
|
Allowed |
Not set |
Access permissions are set to Allowed for services A, B, C but not set for subservice D |
Services A, B, C and subservice D |
If service access is set to Allowed, then all subservice access is automatically set to Allowed |
|
Allowed |
Not Allowed |
Access permissions are set to Allowed for services A, B, C and set to Not Allowed for subservice D |
Services A, B, C |
CA SOI does not support this situation. The user group sees services A, B, C and subservice D. |
|
Not Allowed |
Allowed |
Access permissions are set to Allowed for services A and B and subservice D, but set to Not Allowed for service C. |
Services A, B and subservice D under services A and B only |
|
|
Not Allowed for any parent |
Allowed |
Access permissions are set to Not Allowed for services A, B, C and set to Allowed for subservice D. |
Subservice D |
CA SOI does not support this situation. The user group does not see any service or subservice. However, you can create a placeholder parent service with subservice D and you can set both access permissions to Allowed. |
* This column indicates what the user group expects to see. Unsupported situations are noted in the comments column and what the user group actually sees in CA SOI.
|
Copyright © 2013 CA.
All rights reserved.
|
|