Permissions

Prev Next
  • Published on Apr 21, 2026
Permissions Categories Reveal has various permission categories that help administrators sort and manage user permissions at scale within Reveal. At the most basic level, each individual account represents a user in the Reveal platform. Users can b...
  • Published on Apr 21, 2026
Users are individual accounts in your instance which can be granted access to different projects, areas, and permissions within Reveal. For information about how users function in Reveal, see About Permissions . Once a new Reveal project is crea...
  • Published on Apr 21, 2026
Users are individual accounts in your instance which can be granted access to different projects, areas, and permissions within Reveal. For information about how users function in Reveal, see About Permissions . Once a new Reveal project is crea...
  • Published on Apr 21, 2026
Roles allow you to enable or disable specific permissions that can be exercised in a project, and also limit access to unauthorized areas in the Reveal environment. For information about how roles function in Reveal, and for a list of Reveal’s def...
  • Published on Apr 21, 2026
There are five default roles in Reveal: Admin, Client Admin, Power Reviewer, Processing User, and Reviewer. Each role has its own default set of permissions , which can be edited if needed. Permissions are managed in the Roles page by navigating t...
  • Published on Apr 21, 2026
The permissions matrices outline the default permissions defined for each role. For information on how to edit default permissions, see Assign Permissions . Note By default, the Administrator role has all permissions, any of which can be adj...
  • Published on Apr 21, 2026
Roles allow you to enable or disable specific permissions that can be exercised in a project, and also limit access to unauthorized areas in the Reveal environment. Role groups map the user to the specific role. You can assign as many users as ...
  • Published on Apr 21, 2026
Teams are separate from roles and role groups, but allow extra control over what content – like tags profiles, wordlists, documents, or fields – are visible to users. A user isn’t required to be a part of a team, but leveraging teams makes it si...
Footer Design