Skip to main content

Members and invitations

Someone gains access to an organisation by becoming a member of it. An invitation is how they get there.

The sequence​

You invite an email address and choose the role they will hold. They accept, and become a member.

From that point, two things decide what they can do:

  • Their role — what they can do
  • Their site scope — where they can do it

Both are set on the member, and both can be changed afterwards without re-inviting.

The thing to set at the same time​

Site scope is not part of the invitation. A new member arrives with none, which means unrestricted — they can see every site in the organisation.

So if someone should be limited to one warehouse, setting their role during the invitation is only half the job. The scope has to be added once they are a member, and until it is, they can see everything.

This is the most common way people end up with more access than intended, and nothing flags it.

Membership is per organisation​

Someone can belong to several organisations, with a different role in each. Their account is theirs; their membership is per organisation.

Which organisations a person can see follows from their memberships alone — no role grants visibility of an organisation they do not belong to. On a shared site that matters, because stock visibility follows membership rather than role: see who sees what.

Removing someone​

Removing a member ends their access to that organisation. Their account continues to exist, along with any memberships they hold elsewhere.

What they did remains in the audit log — removing a member does not remove their history.

Every organisation needs an owner​

At least one member must hold the owner role. It is the only role that can manage billing, and the only one whose permissions cannot be edited away.

See invite someone, change someone's role and remove someone.