Skip to main content

Permissions: Overview

Settings > Account Settings > Permissions

Permissions define what users can access and control within the platform, ensuring users only interact with the information and functionality relevant to their responsibilities.


Table of Contents


Overview

Permissions in Buildend control what users are allowed to see and do across the platform.

They are used to ensure users only interact with the areas of the system relevant to their responsibilities.

Permissions are applied through roles and help maintain structured, controlled access across both internal teams and external collaborators.


Why Permissions Matter

Permissions are especially important because Buildend supports both internal users from the organization managing the Workspace, as well as external collaborators such as vendors, subcontractors, and consultants who require controlled access to project information and workflows.

Proper and intentional permission setup helps ensure:

  • Users only see the information relevant to their role.

  • Users can only perform actions they're authorized to complete.

  • Sensitive company and project information remains protected.

  • Internal teams and external collaborators can work together securely.


Permission Levels

Buildend permissions are structured into two levels: Company Level and Project Level.

These define how users interact with organization-wide and project-specific information.

Company Level

Controls access to company-wide settings, administrative tools, and shared resources outside of individual projects.

Project Level

Controls access to information and actions within individual projects, including workflows, documents, and project data.


Understanding Access Types

Buildend permissions use standardized access types to define what users can do within different areas of the platform.

  • ⛔ No Access

    • The user cannot see or interact with the item or module.

  • 👁️ Viewer

    • The user can view information but cannot make changes.

  • ✍️ Editor

    • The user can create and edit/update information within the area they have access to.

  • 🔑 Full Access

    • The user has full control, including the ability to manage, modify, and remove/archive information where permitted.


Permission Roles

Permissions are managed through roles.

A Permission Role is a reusable collection of Company Level and Project Level permissions that can be assigned to one or more users.

Buildend provides two approaches to Permission Roles:

  • System-defined roles that are ready to use out of the box.

    • Learn more in Default Permission Roles [🚧 Coming Soon]

  • Custom roles that can be created when more specific access is required.

    • Learn more in Custom Permission Roles [🚧 Coming Soon]


Areas Available to All Users

Some areas of Buildend are available to all users regardless of their assigned permission role.

These areas support core participation and visibility across the platform and are not restricted by role-based access.

Examples include:

  • Ball In Court

  • User Profile & Personal Settings

  • Tasks

  • Notifications


Quick Reference: Permissions Terminology

Buildend permissions use several related terms. Here's a quick way to remember them:

Term

Description

Permission Level

The scope where permissions apply, either at the:

  • Company Level or Project Level.

Access Type

The type of interaction allowed within an area of the platform:

  • Viewer, Editor, Full Access, No Access.

Permission Role

The assigned role that defines a user’s overall access within Buildend. There are system-defined ones provided out of box, or custom ones can be created.

  • For example: ProjectAdmin or SystemUser

Did this answer your question?