Administration
Two questions decide what someone can do in Yessort, and they are answered separately.
What can this person do? Their role.
Where can they do it? Their site scope.
The two never mix. A role grants capabilities; a scope narrows which sites those capabilities apply to. Changing someone's scope never gives or takes away an ability, and changing their role never changes which sites they see.
Keeping them apart is what makes access predictable. See how access works.
Roles are labels over a matrix
Every organisation has the same five roles: owner, admin, member, warehouse and read-only.
What each one grants is yours to change. Yessort never checks a role by name — every check resolves through the permission matrix — so re-pointing what "member" means changes behaviour immediately, with no release needed.
The exception is owner, which is fixed. It is the backstop that stops an organisation locking itself out.
One rule about scope, worth knowing now
Someone with no site restrictions can see every site. Not none.
Site scope works by listing the sites a person is limited to. No entries means no limits, so a person you have never scoped has access to everything in the organisation.
It is the opposite of what most people assume, and it fails quietly — the person simply sees more than intended. See site scope.
Your settings and the organisation's
Two different places, and the split is mostly clean.
Yours — your profile, your password and security, your active sessions, and which notifications you receive. They follow you across every organisation you belong to.
The organisation's — members, invitations, teams, roles, billing, the audit log, and organisation settings. These need organisation-admin access and affect everyone.
One thing sits awkwardly across the line: API keys are managed under your own settings but authorise access on behalf of the whole organisation. See your account and your organisation.
Concepts
- How access works — the two axes, and why they stay separate.
- The five roles — what each is for.
- Editing what a role can do — changing a role's permissions for your organisation.
- Site scope — limiting someone to particular sites.
- Members and invitations — how someone joins.
- Teams — what a team is, and what it does not do.
- The audit log — the record of what changed.
- Trading brands — the brand your orders and documents carry.
- Feature toggles — switches that turn parts of Yessort on.
- Your account and your organisation — which settings are which.
How to
- Invite someone
- Change someone's role
- Limit someone to certain sites
- Edit a role's permissions
- Remove someone
- Create a team
- Manage billing
- Create an API key
- Manage your sessions and notifications