Inviting the team and picking a role

The permission tier is what someone can do. The job title is what you call them on cards and reports. Mix them however the studio talks — a “Project Lead” can still be a Manager in Beech.

The three tiers

• Admin — whole firm, billing, export, archive/restore. Counts as a seat. There must always be at least one.
• Manager — projects, sprints, vendors, invites, reviews. Can view Billing; cannot renew or delete the firm. Counts as a seat.
• Contributor — create and assign work on projects they belong to, site visits, reviews. Counts as a seat.

Send an invite

1. 1
   Firm settings → Members → Invite

   Email, tier, optional job title. Only Admins can invite new Admins. The link is valid for 7 days.

2. 2
   They set a password

   After they accept, they count toward the seat cap. Resend or revoke from Pending invites if needed.

Edit a row to change tier or title immediately. Deactivate when someone leaves — they cannot log in, they drop out of pickers, and the seat frees at once. History stays. Only deactivated users can be permanently deleted by an Admin; open tasks go Unassigned.

Prerequisites

• Confirm you can access the project and the page referenced in this workflow.
• Collect any drawing references, due dates, and ownership details before you start.

Expected outcome

By the end of this workflow, your team has one visible, repeatable process and cleaner handovers.

Common mistakes and prevention

• ✓

  Mistake 1: Skipping context fields (owner, due date, status notes), which makes follow-up harder.

• ✓

  Mistake 2: Treating chat updates as source of truth instead of recording the update in Beech.

Troubleshooting checklist

1. 1
   Troubleshooting step 1

   If a control is missing, verify your role has permission for the action.

2. 2
   Troubleshooting step 2

   If results look wrong, check filters and refresh to confirm latest synced data.