Skip to main content
Permission Groups allow you to define roles with specific access levels for organization management and project access. Assign members to groups to control what they can see and do.

​
Default Permission Groups

Boltz provides four default permission groups that cover common organizational roles:

​
Editing Permissions

​
Understanding Permission Levels

​
Admin Access

Controls access to organization-level settings and management features.

​
Project Access

Controls what members can do within Design Projects.

​
Configuring Permission Groups

​
Viewing Group Members

Click the Members button next to any group to see which users are assigned to it. Click the Permissions button to modify a group’s access levels:
  1. Organization management - Select the admin access level
  2. Project access - Select the project access level
  3. Click Save to apply changes
Be careful when modifying or assigning the group permissions so that users only have access to appropriate content

​
Permission Group Assignments

Members can belong to multiple permission groups. When a member belongs to multiple groups, they receive the highest permission level from any of their groups. Example: A user in both “All Members” (Write) and “Scientist” (Own) groups will have Own access to projects.

​
Common Configurations

  • Principal Investigators → Admin + Scientist groups
  • Postdocs/Senior Scientists → Scientist group
  • Graduate Students → All Members group
  • External Collaborators → Viewer group
  • Department Heads → Admin group
  • Computational Chemists → Scientist group
  • Medicinal Chemists → All Members group
  • Management/Stakeholders → Viewer group
  • Account Managers → Admin group
  • Project Scientists → Scientist group
  • Clients (read-only access) → Viewer group

​
Creating Custom Permission Groups

Custom permission group creation may be available.Contact support for details.

​
Best Practices

Principle of least privilege: Assign the minimum permissions necessary for each role. Start with restrictive access and expand as needed.
Use All Members as a baseline: Keep all users in the “All Members” group for basic platform access, then add specialized groups for elevated permissions.
Document your permission structure: For larger organizations, maintain documentation of which roles map to which permission groups.