Skip to main content

Change someone's role

Under the organisation's Members. Needs organisation-admin access.

Steps​

  1. Open Members and find the person.
  2. Change their role.
  3. Save.

It takes effect immediately. They do not need to sign out and back in.

What a role change does not affect​

Their site scope. Where they can work is a separate setting and is unchanged. Someone limited to one warehouse who becomes a member is still limited to that warehouse.

The exception: promoting someone to admin or owner removes any site limits, because those roles are never site-restricted. Worth knowing if you are widening someone's role for a narrow reason — you may be widening where they work as well.

Their history. What they did under their old role stays in the audit log.

Their other organisations. Roles are per organisation. Making someone an admin here grants nothing anywhere else.

Every organisation needs an owner​

Changing the last owner to something else would leave the organisation without one — and owner is the only role that can manage billing or edit roles unconditionally.

Appoint the new owner before demoting the old one.

If the change seems to do nothing​

Check whether your organisation has edited what that role grants. Role names are labels over a permission matrix you control, so "member" here may not mean what it does elsewhere.

Also check site scope. Someone who still cannot see what you expected may be limited to sites rather than short of permissions — a different problem with a different fix.

Widening versus narrowing​

Narrowing is safe to do promptly; the person loses access they should not have had.

Widening deserves a moment. Granting update on a resource without read produces a role that can change something it cannot see, and admin brings the loss of site limits described above.