Users & their Roles

The following tables describe the list of actions performed by all the users in the ACC.

The first table here describes the actions of User, Super User, Consumer:

Actions to be Performed User Super User Consumer
Directory Level Permission
(Within the same organization)
View View View
Directory Level Permission
(Other organization)
None None None
Directory Privileges on
Agent Repository Page
None None None
Can Move the agents from one
Directory to another
Yes Yes No
Can Deploy the agents on Cluster Yes Yes No
Can run the agents on Cluster Yes Yes No
Can delete the agent from Agent Repository No Yes No
Can Download Log and Data file Yes Yes Yes
Can View Input parameters Yes Yes Yes
Can Restart the agent Yes Yes No
Is Audit Trail option available No No No
Job Level Schedule permission View/Add/
Edit/Disable
View/Add/
Edit/Disable
View
Rate Limit Feature permission None None None
Ticketing System
(within Organization)
View View/Edit
/Add/Close/
Update
View/Edit/
Add/Close/
Update
Ticketing System
(Across Organization)
None None None
Proxy level permission View  View None
Pool level permission View View None
Organization Level permission None None None
User Level permission
(Creation, Edition, Deletion)
None None None
Access for ACC Desktop Yes Yes No
Server Level permission
(View/Add/Edit/Delete)
None None None
Ability to switch from one
Organization to another org.
No No No
Download SCGX Yes Yes No
Running Agents
(Agents->Running Agents)
No No No
Directory Audit Trail No No No
API Access No No No
Cluster Information
(View/Add/Edit/Delete)
No No No
Can create Directory No No No
Can approve/disapprove the agent No No No
Can add the Schedule for Approve agent Yes Yes No
Can enable/disable the schedules for Approve agent Yes Yes No

 

The second table here describes the actions of Consumer Admin, Supporter and Supporter Admin:

Actions to be Performed Consumer Admin Supporter Supporter Admin
Directory Level Permission
(Within the same organization)
View View View
Directory Level Permission
(Other organization)
None None None
Directory Privileges on Agent Repository Page None None None
Can Move the agents from
one Directory to another
No No No
Can Deploy the agents on Cluster No No No
Can run the agents on Cluster No No No
Can delete the agent from Agent Repository No No No
Can Download Log and Data file Yes Yes Yes
Can View Input parameters Yes Yes Yes
Can Restart the agent No No No
Is Audit Trail option available No No No
Job Level Schedule permission View View View
Rate Limit Feature permission None None None
Ticketing System
(within Organization)
View/Edit/
Add/Close/
Update/Delete
View/Edit/
Add/Close/
Update
View/Edit/
Add/Close/
Update/Delete
Ticketing System
(Across Organization)
None None None
Proxy level permission None None None
Pool level permission None None None
Organization Level permission None None None
User Level permission
(Creation, Edition, Deletion)
None None None
Access for ACC Desktop No No No
Server Level permission
(View/Add/Edit/Delete)
None None None
Ability to switch from one
Organization to another org.
No No No
Download SCGX No No No
Running Agents
(Agents->Running Agents)
No No No
Directory Audit Trail No No No
API Access No No No
Cluster Information
(View/Add/Edit/Delete)
No No No
Can create Directory No No No
Can approve/disapprove the agent No No No
Can add the Schedule for Approve agent No No No
Can enable/disable the schedules for Approve agent No No No

 

The third table here describes the actions of Admin, Super Admin, Server Admin:

Actions to be Performed Admin Super Admin Server Admin
Directory Level Permission
(Within the same organization)
View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Directory Level Permission
(Other organization)
None View/Add/
Edit/Delete
View
Directory Privileges on
Agent Repository Page
Yes Yes Yes
Can Move the agents from
one Directory to another
Yes Yes No
Can Deploy the agents on Cluster Yes Yes No
Can run the agents on Cluster Yes Yes No
Can delete the agent from
Agent Repository
Yes Yes No
Can Download Log and Data file Yes Yes No
Can View Input parameters Yes Yes No
Can Restart the agent Yes Yes No
Is Audit Trail option available Yes Yes No
Job Level Schedule permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Rate Limit Feature permission View View/Add/
Edit/Delete
View/Add/
Edit/Delete
Ticketing System
(within Organization)
View/Add/
Edit/Delete/
Close
View/Add/
Edit/Delete
None
Ticketing System
(Across Organization)
None View/Add/
Edit/Delete
None
Proxy level permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
View/Add/
Edit/Delete
Pool level permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
View/Add/
Edit/Delete
Organization Level permission None View/Add/
Edit/Delete
View/Add/
Edit/Delete
User Level permission
(Creation, Edition, Deletion)
View/Add/
Edit/Delete
View/Add/
Edit/Delete
View/Add/
Edit/Delete
Access for ACC Desktop Yes Yes Yes
Server Level permission
(View/Add/Edit/Delete)
View View/Add/
Edit/Delete
View/Add/
Edit/Delete
Ability to switch from one
Organization to another org.
No Yes Yes
Download SCGX Yes Yes No
Running Agents
(Agents->Running Agents)
Yes Yes Yes
Directory Audit Trail Yes Yes Yes
API Access Yes Yes Yes
Cluster Information
(View/Add/Edit/Delete)
Only View Yes Yes
Can create Directory Yes Yes No
Can approve/disapprove the agent Yes Yes Yes
Can add the Schedule for Approve agent Yes Yes No
Can enable/disable the schedules for Approve agent Yes Yes No

 

The fourth table here describes the actions of Reporting*, Org Super Admin, and Compliance:

* Reporting: The Reporting user role works when it is combined with the Super Admin role and hence the reporting user has all the required privileges that a Super Admin user has. The additional privilege that gets added with the Reporting role is that the user will be able to receive email notifications across multiple organizations. So this privilege is useful only when, you are managing multiple organizations in the AgentControlCenter and want to keep a track of all the failures or successes or new ticket email notifications.

Actions to be Performed Reporting* Org Super Admin Compliance
Directory Level Permission
(Within the same organization)
View/Add/
Edit/Delete
View/Add
/Edit/Delete
View
Directory Level Permission
(Other organization)
View/Add/
Edit/Delete
None None
Directory Privileges on Agent Repository Page Yes Yes View
Can Move the agents from one Directory to another Yes Yes No
Can Deploy the agents on Cluster Yes Yes No
Can run the agents on Cluster Yes Yes No
Can delete the agent from Agent Repository Yes Yes No
Can Download Log and Data file Yes Yes Yes
Can View Input parameters Yes Yes Yes
Can Restart the agent Yes Yes No
Is Audit Trail option available for agent Yes Yes

Yes

Job Level Schedule permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Rate Limit Feature permission View/Add
/Edit/Delete
View/Add/
Edit/Delete
View
Ticketing System
(within Organization)
View/Add/
Edit/Delete/
Close
View/Add/
Edit/Delete/
Close
View/Add/
Edit/Close
Ticketing System
(Across Organization)
View/Add/
Edit/Delete
None None
Proxy level permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Pool level permission View/Add
/Edit/Delete
View/Add/
Edit/Delete
View
Organization Level permission View/Add/
Edit/Delete
View/Add/
Edit/Delete
None
User Level permission
(Creation, Edition, Deletion)
View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Access for ACC Desktop Yes Yes No
Server Level permission
(View/Add/Edit/Delete)
View/Add/
Edit/Delete
View/Add/
Edit/Delete
View
Ability to switch from one
Organization to another org.
Yes No No
Download SCGX Yes Yes No
Running Agents
(Agents->Running Agents)
Yes Yes View
Directory Audit Trail Yes Yes Yes
API Access Yes Yes No
Cluster Information
(View/Add/Edit/Delete)
Yes Yes No
Can create Directory Yes Yes No
Can approve/disapprove the agent
Yes Yes Yes
Can add the Schedule for Approve agent
Yes Yes No
Can enable/disable the schedules for Approve agent
Yes Yes No

 

Was this article helpful?
0 out of 0 found this helpful

Comments

2 comments

  • If I'm reading this right, a Reporting user is more powerful than a Super Admin as they can do everything a Super Admin can plus close "Ticketing System (within Organization)".  I would have never expected that based on name alone.  Why on earth would a Reporting user need that much power?

    0
  • Hi William,
    Thank you for bringing this to our notice. We have updated our documentation and have added the actual usage of the Reporting User Role.
    The reporting user role can be used to receive email alerts across organizations. For example, if you have 2 or more organizations crated in your ACC and you want to get email notifications and you want to have monitoring in place across the entire ACC then you can use the Reporting Role along with the Super Admin role.

     This reporting role can only be used along with the 'Super Admin' role. 

    1

Please sign in to leave a comment.