Skip to main content

Roles and Permissions Overview

This guide provides an overview of how user roles and permissions work in Authorium and explains the difference between organization and project roles. It also outlines how these roles ensure the right level of access for each user while maintaining security and data integrity.

When to Review User Roles and Permissions​

You should review user roles and permissions when:

  • You are setting up a new Authorium organization or project.
  • You need to adjust access levels for users.
  • You want to ensure compliance with your organization’s security and data policies.

Understanding the Role-Based Permissions System​

Authorium uses a role-based permissions system, where each user is assigned to one or more roles with specific access rights. This approach ensures that users can perform their tasks effectively while protecting organizational data.

There are two main types of roles in Authorium:

Organization Roles​

Define permissions at the organization level, controlling access to:

  • Organization-wide settings.
  • Authentication and security configurations.
  • Member management.

Default organization roles include:

  • Account Owner – Full control over the organization and its settings.
  • Admin – Broad permissions to manage the organization but with some restrictions compared to the Account Owner.
  • Project Creator – Can create and manage projects but with limited access to organization-level settings.

Project Roles​

Define permissions at the project level, controlling access to:

  • Project-specific resources.
  • Documents, templates, and workflows.
  • Project member management.

Default project roles include:

  • Project Owner
  • Project Manager
  • Editor
  • Contributor
  • External Guest
  • Reviewer
  • Viewer
Custom Project Roles

In addition to the default roles listed above, you can create custom project roles tailored to your organization’s specific permission needs.

This section includes: