Which permissions are available for Team Roles?

The Brandle Presence Manager offers two (2) primary User Roles to start:

• Entity Admin - all permissions available.
• View-only User - View only.

An administrator for your corporate entity account also selects the permissions per custom Team Roles that s/he creates specifically for your company.

The tables below identify which features are enabled or available for each user role. The permissions enabled (✓) for Entity Admin and View-only users are not editable. However, customized Team Roles have optional permissions. The custom Team Roles created are general Entity Users (as titled in the tables below). The Entity User has a (●) set of permissions. Permissions are set per custom Team Role, so everyone assigned one of these roles will all have the same permissions.

Inventory

Discovery

Tags

General

Identities/Patrolling

Contacts

Reach Forms & Campaigns

Tag Trees

Compliance (GRC)

Legend:

✓ = Supported
○ = Configurable on a per-team role basis, OFF by default.
● = Configurable on a per-team role basis, ON by default.

Updated Team Role Permissions 2020

To add or subtract permissions, just go to Account> Team Roles and select a Role. then click the 3-bar menu and select Edit Permissions. Administrators have ALL boxes checked, so select another Team Role to update any permissions (or create new ones).

There are new Permissions such as:

• Create and Modify Documents (Now that documents have been added)
• Password Vault permissions for those customers with Password Vault
• New Domain-specific Permissions (below the fold of the image below)
• The ability to invite new users (below the fold of the image below)

A note about Tasks: although Tasks is a new feature, we believe that everyone should have access to Tasks, so we did not make a special Permission for them. 

A note about Pop Posts: we also believe that if someone has access to GRC module, that they would have permissions for Pop Posts, if the POP Post Governance feature set is licensed.

And as always recommended, you may want to reserve the ability to Create and Modify Tags for Administrators ONLY. This is incredibly helpful to ensure reports are accurate and your tagging system is kept clean. Instead of having multiple Administrators, you may want to consider creating a role that has all permissions checked except the ability to add or modify tags, and other critical permissions essential to your governance control.

See Also

• What is a User Account?
• Setting Permissions for Entity Users
• What does each User Permission mean?