Memberships & Roles

Memberships are the links between users and entities in Pasco Cloud. Every time you join an organisation, project, or group, a membership record is created that defines your role and context within that entity.

What Are Memberships?

A membership is the relationship between a user and an entity — an organisation, project, or group. Memberships carry important information:

• Role — whether you are an admin or a member
• Title — your specific title within this entity (e.g. "Site Supervisor" on a project)
• Team — which team you belong to within the entity (e.g. "Structural" or "Electrical")
• Job title — your role description within this specific context

These fields let you describe what someone does within a particular organisation or project, which may differ from their general profile information.

ℹ️ Did you know?

A membership title is specific to the entity — it describes your role on this project or in this organisation. It is separate from the job title on your user profile, which is your general professional title. For example, your profile might say "Senior Engineer" while your membership title on a project says "Lead Structural Inspector".

Roles

Every membership has one of two roles:

Admin

Admins have full control over the entity. They can:

• Add and remove members
• Change member roles
• Edit entity settings and details
• Delete the entity
• Manage all content within the entity

Member

Members have standard access. They can:

• View the entity and its content
• Create documents within the entity's context
• Participate in workflows (approvals, comments, assignments)

The specific capabilities vary depending on the entity type, but the principle is consistent — admins manage, members participate.

Memberships Are Explicit

An important concept in Pasco Cloud is that memberships do not cascade. Being a member of an organisation does not automatically make you a member of that organisation's projects. Each membership is created explicitly at each level.

This gives you precise control:

• A subcontractor can be a member of your organisation without seeing every project
• A consultant can be added to a specific project without joining the parent organisation
• A safety officer can be in a group for sharing templates without being part of the project team

Typical Setup

For most construction teams, the setup looks like this:

1. Organisation membership — your company's team members
2. Project memberships — specific people assigned to each project
3. Group memberships — people organised by function or team for sharing purposes

Permissions by Entity Level

Organisation Admin

• Edit organisation details (name, logo, industry, address)
• Manage organisation members (invite, remove, change roles)
• Request organisation verification
• Create projects under the organisation

Organisation Member

• View organisation details and member list
• Access organisation-scoped documents shared with them

Project Admin

• Edit project details (name, description, dates, status)
• Manage project members (invite, remove, change roles)
• Link organisations to the project

Project Member

• View project details and member list
• Create and manage documents within the project context

Group Admin

• Edit group details (name, description)
• Add and remove group members
• Change member roles within the group

Group Member

• View the group and its member list

Managing Memberships

Inviting Members

To add someone to an organisation, project, or group:

1. Navigate to the entity's detail page
2. Click the Members tab
3. Click Invite or Add Member
4. Enter their email address or select from existing users
5. Set their role (admin or member) and optionally set a title and team

If the person is not yet on the platform, they will receive an email invitation to join. Once they create their account and accept, they will be added as a member.

Changing Roles

Entity admins can change any member's role between admin and member at any time. This takes effect immediately.

Removing Members

Entity admins can remove members from the entity. Removing a member does not delete any documents they created — it only removes their access to the entity.

What's Next?

• Put this into practice with the tutorial on inviting your team
• Learn how memberships relate to groups and sharing
• Explore how organisations and projects use memberships