3.1 Roles and Capabilities
- Shane Pierce
- Laura McWilliams
3.1.1 Ordinary Users
Each person defined to Isora GRC can be associated with one or more organizational units (OUs). For each OU a person is involved with, the person has a role within the OU. The following table summarizes the capabilities of each role.
Role | Capabilities (for a given Organizational Unit) |
|---|---|
Organizational Unit Head | Can final acknowledge an org unit survey; can see all reports (including child OU reports); can answer survey questions |
Assessment Manager | Can launch survey; can view reports and answer survey questions; can delegate OU questions (and add users via delegation) and assign hosts to users; can view all permissions and assign permissions to other users, can edit sheets |
IT Staff | Can view reports and answer survey questions; can delegate OU questions (and add users to Isora GRC via delegation) and assign hosts to users; can edit sheets |
Auditor | Has read-only access to everything |
(no role assigned) | Can do categorization of hosts that belong to them; can answer any unit questions that have been delegated to them; can create sheets and edit sheets that belong to them (irrespective of organizational unit) |
Some versions of Isora GRC also have a User role, but the User role does not confer any specific capabilities. If can be thought of as a way to designate a person as being associated with a particular OU.
3.1.2 Superusers
In addition to ordinary persons, Isora GRC must have at least one administrative person defined. This is indicated by the “superuser” attribute. Initially, Isora GRC is set up with at least one superuser defined. A superuser can do everything encompassed by all of the ordinary person roles, and much more. Any superuser can do everything in Isora GRC. The following table summarizes what superusers can do (in addition to all the things ordinary users can do):
Designation | Capabilities (not limited by Organizational Unit) |
|---|---|
superuser | Can view, edit, add or remove people, OUs and permissions, sheets and hosts; can view, edit, add or remove all question objects, can create, edit or remove assessments |
3.1.3 Service Accounts
Any user that you create in Isora GRC may be designated as a “service account” using a checkbox. A service account should be used for any non-person entity that needs to access Isora GRC. Like an ordinary person, a service account may have roles in OUs assigned to it. No remote authorization checks are performed with service accounts. Although it is possible to authenticate a service account locally, by specifying a local password, or to authenticate it remotely via LDAP, it is not typical for a service account to log into the Isora GRC web interface. Service accounts should access Isora GRC through the API using a token. You can learn more about the API in the https://saltycloud.atlassian.net/wiki/spaces/SHD/pages/5013505 .
Next: 3.2 Adding new people and defining their roles in Isora GRC
If you can't find what you are a looking for and need support, email support@saltycloud.