Editing what a role can do
The five role names are fixed. What each one grants is yours to change, for your organisation, without affecting anyone else's.
Why the change takes effect at once
Yessort never checks a role by name. Every decision resolves through a matrix of resources and actions — can this person update inventory, can they approve a supplier document.
A role is a bundle of entries in that matrix. Re-pointing the bundle changes behaviour immediately: nothing needs releasing, because no code says "if warehouse, then".
That is also why the role names should be read as labels for whatever you have decided they mean, rather than as fixed job descriptions.
Owner cannot be edited
Owner ignores any changes made to the others, and its own permissions cannot be altered.
Without that, an organisation could edit away every route to administering itself and have no way back. Owner is the guarantee that at least one person can always put things right.
The roles editor is itself a permission
The ability to edit roles is an entry in the matrix like any other, which means it can be granted or removed — and it is guarded so the editor cannot be used to remove your own ability to use it.
Beyond that guard, take care: it is possible to make a role considerably less useful than intended, and the people affected will not know why their screens changed.
What is worth changing
Narrowing a role is the common case — a member who should not read costs, a warehouse user who should not see customers.
Widening is worth more thought. Granting update on a resource usually implies granting read too, and a role that can change something it cannot see is a confusing thing to hold.
Changes apply to everyone with that role
Editing a role affects every member holding it, immediately. There is no per-person override.
If one person needs something different, the options are to give them a different role, or to change what that role grants for everyone. Yessort has no per-member permissions.
Where to look first
The full list is in the permission matrix. Three entries surprise people:
goods_receipthas onlyaccept— there is no read permission for it. Purchasing pages are read through the supplier permission- Managing billing is owner-only — an admin can read billing and nothing you grant will let them manage it
organization,member,invitationandteamcarry no read action at all