Skip to main content
This page explains who can view and edit clients, properties, and projects, and how access is scoped to your organization. Permissions throughout the product are based on a user’s role. The roles referenced here are: Admin, Ops Manager, Sales Admin, Sales Member, Client Coordinator, and Crew Leader. “Branch Management” is not a separate role you assign — it’s a shorthand for Admin, Ops Manager, Sales Admin, and Client Coordinator together, the roles that see all of a branch’s records rather than only their own.

​
How access is scoped

All viewing and editing of clients, properties, and projects is bounded by the organization(s) a user belongs to:
  • A user only sees and edits records that belong to an organization they are a member of.
  • A user who belongs to no organization sees nothing and can edit nothing.
  • If a user has selected a specific organization (tenant) and has access to it, results are narrowed to exactly that organization. Otherwise, results span all of the user’s organizations.
Organization membership is the hard boundary. Belonging to the organization is what determines whether a user can access these records at all. On top of that, some screens are additionally scoped to your active branch: the Clients list defaults to the branch you’re currently working in, but a Branch filter lets you switch the list to any other branch you belong to — and, if you can see all clients, to clients that don’t have a project yet (Unassigned). Opening a client’s summary while the Branch filter points at another branch switches your active branch to match, and opening a project that belongs to a different branch prompts a branch switch (or shows “not found” if you don’t have access to that branch).

​
Clients

​
Viewing clients

Any signed-in user may view clients within their organization. No specific role is required to view — every role can see the clients in organizations they belong to.

​
Creating clients

Clients are normally created by converting a lead (publishing a lead activity), not by a standalone “create client” action. Directly creating a client is limited to Admin, scoped to an organization the user belongs to.

​
Editing clients

Every role can edit a client, scoped to the user’s organization(s).

​
Deleting clients

Deleting a client requires one of: Admin, Ops Manager, or Sales Admin, scoped to the user’s organization(s). Other roles can edit clients but cannot delete them.

​
Properties

​
Viewing properties

Any signed-in user may view properties within their organization. No specific role is required to view.

​
Creating properties

Creating a property is limited to Admin, under an organization the user belongs to.

​
Editing properties

Every role can edit a property, scoped to the user’s organization(s).

​
Deleting properties

Deleting a property is limited to Admin, scoped to the user’s organization(s).
When a property’s address changes, its location (latitude/longitude) is updated automatically. This happens behind the scenes and is not a permission control.

​
Projects

​
Viewing projects

Any signed-in user may view projects within their organization. No specific role is required to view.

​
Creating projects

Creating a project requires one of: Admin, Sales Admin, Sales Member, or Client Coordinator, under an organization the user belongs to.
Ops Manager and Crew Leader cannot create projects.

​
Editing projects

Editing a project requires one of: Admin, Ops Manager, Sales Admin, Sales Member, or Client Coordinator, scoped to the user’s organization(s).

​
Deleting projects

Deleting a project requires one of: Admin, Sales Admin, or Sales Member, scoped to the user’s organization(s). Ops Manager and Client Coordinator can edit projects but cannot delete them.

​
Quick reference

​
Notable points

  • Viewing and editing clients and properties are open to all roles (within the user’s organization), but creating and deleting are tightly role-gated as shown above.
  • Creating clients and properties is reserved for Admin — and clients in practice are created by converting a lead, not through a standalone create action.
  • Project deletion is the sales roles (Admin, Sales Admin, Sales Member); Ops Manager and Client Coordinator can edit projects but cannot delete them.
  • Organization membership is the hard access boundary for clients, properties, and projects — but client lists and project pages are additionally scoped to your active branch. On the Clients list, the Branch filter lets you see another branch’s clients directly; elsewhere, switch branches to see another branch’s records.