Roles and Disciplines Guide

Understanding Roles

Available Roles (Highest to Lowest Access)

1.Owner

• Full project control
• Can manage all settings and permissions
• Can assign roles and disciplines
• Cannot be removed by other roles

2.Approver

• Reviews and approves work
• Can manage team members (if permitted)
• Can oversee multiple disciplines
• Reports to Owner

3.Task Team

• Standard team access
• Creates and edits content
• Works within assigned disciplines
• Basic collaboration features

4.Consumer

• View-only access
• Can see assigned content
• Cannot make changes
• Perfect for external stakeholders

Understanding Disciplines

Default Disciplines

Your project starts with five standard disciplines:

1. ARC - Architecture
2. ENG - Engineering
3. MEP - Mechanical, Electrical, Plumbing
4. OTHER - Miscellaneous items
5. SHARED - Common access area

How Disciplines Work

• Team members can belong to multiple disciplines
• Files can be tagged with specific disciplines
• Access is limited to assigned disciplines
• SHARED discipline is accessible to all members

Permissions Overview

Owner Permissions

• Manage roles and disciplines
• Control billing and settings
• Manage team members
• Send invitations
• Full access to all features

Approver Permissions

• Review work in assigned disciplines
• Manage team members (if granted)
• Update tickets
• Send invitations (if granted)

Task Team Permissions

• Create and edit content
• Update tickets
• Work within assigned disciplines
• Basic collaboration tools

Consumer Permissions

• View assigned content
• Read-only access to files
• See team updates
• No editing capabilities

Best Practices

Role Assignment

• Keep Owner role limited
• Use Approver for team leads
• Assign Member as default
• Use Consumer for external viewers

Discipline Management

• Assign relevant disciplines to each member
• Use SHARED for common resources
• Review assignments regularly
• Keep discipline structure simple

File Organization

• Tag files with correct disciplines
• Use SHARED for team-wide content
• Consider cross-discipline needs
• Maintain clear folder structure

Security Notes

• Task Team members only see content in their disciplines
• Role changes require Owner approval
• All actions are logged
• Regular access reviews recommended