Docs/Team
● Team

Roles,
permissions and access.

Access is scoped by the work someone does, so the packing bench never sees supplier pricing.

The model

A role is a set of permissions, and each permission maps to an area of the platform. Navigation is built from the same permissions, so someone without access to purchasing does not see purchasing — rather than seeing it and being refused.

The two working roles

OfficePlanning and commercial

Listings, pricing, purchasing, stock planning, customer messaging and reporting.

WarehousePhysical operations

Picking, packing, dispatch, counts, transfers and goods receipt.

The split is deliberate: the office role decides what should happen, the warehouse role executes what is physically in front of them. Most access problems disappear once that line is drawn.

Inviting and removing

  1. Invite by email from Settings → Users and assign a role.
  2. The invite is single-use; the person sets their own password.
  3. To remove access, deactivate the user rather than reusing the login. History stays attributed to the person who did the work.
Shared logins break accountability. One login per person is what makes a stock movement or a price change explainable months later. A shared warehouse account cannot answer "who changed this".