Permissions & Participants in Actions

Summary

This article explains how Action visibility and permissions work in BuilderPal—who can see an Action, who can interact with it, and how roles affect editing, assigning, and deleting.

Prerequisites

• You understand your team role (Admin, Project Manager, Supervisor, Team Member, etc.).
• You have access to at least one project.

How Action Visibility Works

Action visibility is based on project access and participation.

You can see an Action if:

• You are assigned to it.
• You are added as a participant.
• You are part of the project where the Action exists.
• You belong to a team involved in the Action (GC or Sub).

There is no follower mode and no read-only mode.
If you are a participant, you can see the entire Action.

You cannot see an Action if:

• You do not have access to the project.
• You are not assigned or added as a participant.
• Your team is not involved in the Action.

What Participants Can Do

All participants—regardless of role—can:

• View all Action details
• Comment on the Action
• Upload attachments
• Complete the Action
• Reassign the Action (to internal team members or subcontractors, depending on role)

Participants always see the full Action, including attachments, descriptions, comments, fields, and history.

Editing and Deletion Rules

Editing and deletion are determined by role permissions, not participation.

• Admins, Project Managers → Full edit + delete
• Team Members, Supervisors → Can edit most fields; cannot delete unless allowed
• Subcontractors → Can edit/comment/complete assigned Actions; cannot delete GC-created Actions

Assigning Actions

All users can assign Actions.

When assigning:

• The Team Members tab shows your internal company members.
• The Subcontractors tab shows all hired trades on the project.

GCs can assign Actions to subcontractors.
Subcontractors cannot assign Actions to GC users or GC team members.

Actions do not move between projects.
They stay inside the project where they were created.

Action Permissions Across Project Types

GC-Owned Projects

GC team members can:

• Create Actions
• Assign Actions to internal users or subcontractors
• Edit and manage all Actions (role-based)
• See every Action inside the GC project

Subcontractors can:

• See and work on Actions assigned to them
• Create Actions for themselves within the subcontractor scope

Subs cannot:

• Assign Actions to GC users
• See GC-internal Actions

Subcontractor-Owned Projects

These projects belong exclusively to the subcontractor’s company.

Subcontractors can:

• Create, edit, and manage all Actions in their own project
• Assign Actions to other members of their team
• Manage their internal schedule

GCs:

• Cannot access the subcontractor’s project
• Only see surfaced documents and limited activity inside their GC project
• Cannot see or create Actions in the subcontractor project unless directly assigned (rare)

My Tasks

Every user has a private project called My Tasks.

• Only the individual user can access it.
• Even Admins cannot view it unless explicitly invited.
• Users can create and manage personal Actions.

This space is ideal for private notes, drafts, and personal planning.

Editing and Deletion Permissions

Editing and deleting Actions follow role permissions:

• Admins → Full permissions
• Project Managers → Full project-level Action management
• Team Members / Supervisors → Edit most content; deletion depends on permissions
• Subcontractors → Edit assigned Actions; cannot delete GC-created Actions

Participation does not override these permissions.

Summary Table

Related Articles

• Roles & Permissions Overview
• Project Access Explained
• Office Permissions and Access
• Manage Team Member Permissions