Skip to main content

Default Permission Roles

User Menu > Settings > Account Settings: Permissions

Buildend includes a set of default permission roles for both Company Level Permissions and Project Level Permissions. These roles are designed to meet the needs of most organizations and provide a recommended starting point for managing user access.

Table of Contents


Overview

Buildend includes a set of default permission roles out of the box that have been designed to meet the needs of most construction organizations.

We recommend starting with these default roles before creating any custom permission roles. In most cases, they provide the appropriate level of access without additional configuration.

Default permission roles are available for both Company Level and Project Level permissions:

📝 Note: If your organization consistently requires a level of access that falls between the default permission roles, consider creating a custom permission role.


Company Level Defaults

Company Level Permission Roles control access to workspace-wide features such as shared resources, administrative settings, and system configuration.

Default Role Name

Typical Users

SystemAdmin

Buildend Administrators, IT Administrators

SystemUser

Office Staff, Operations, Project Managers

SystemExternalUser

Any external collaborators who require login access


Project Level Defaults

Project Level Permission Roles control access within individual projects and determine how users interact with project information.

Default Role Name

Typical Users

ProjectAdmin

Project Managers

ProjectUser

Project Coordinators, Site Superintendents, Foremen

ProjectExternalUser

Consultants, Architects, Vendors, Subcontractors

📝 Note

These examples reflect common usage patterns and are intended as a starting point. The appropriate permission role depends on each user's responsibilities within your organization, so be sure to review the permissions included with each role before making your selection.


Best Practices

When assigning permissions:

  1. Start with the default permission roles.

  2. Select the role that best reflects the user's responsibilities.

  3. If your organization consistently requires permissions that fall between the default roles, create a custom permission role.

This approach helps:

  • Maintain consistent permission structures.

  • Simplify user administration.

  • Reduce unnecessary custom permission roles.

  • Keep permissions easier to review and manage over time.

Did this answer your question?