Brim Permissions

Brim uses a two-tier permission system to help organizations manage access and responsibilities across their projects: General Permissions and Project-Level Permissions.

General Permissions

General permissions apply across the entire Brim platform and determine a user’s ability to create and administer projects.

• Administrator

  Grants full access to all settings and actions across Brim, including managing users and projects globally.

• Can add project

  Allows the user to create new projects within Brim. This permission does not automatically grant access to existing projects.

  • NOTE: This permission is on the "Permissions" tab under a user.

Project-Level Permissions

Project-level permissions define what a user can do within a specific project. These permissions can be customized per project, allowing fine-grained control. You can manage these in the "Project Permissions" section for each project.

The available project-level permissions are:

• Can upload to project

  Allows the user to upload files or data to the selected project, and create and manage variables and dependent variables.

• Project owner

  Grants full control over the project, including editing settings and permissions. Typically used for users who created the project.

• Can manage project team

  Lets the user add or remove team members from the project and assign project-level permissions.

• Can delete documents

  Permits the user to permanently delete documents within the project. Use with caution.

Best Practices

• Assign the Administrator role only to trusted users who need full platform-wide control.
• Use Project owner and Can manage project team to delegate responsibility on a per-project basis.
• Avoid giving Can delete documents access unless absolutely necessary, to prevent accidental data loss.

To edit Permissions as an Admin:

To add users and edit Project-Level permissions as a Project Team Manager: