Platform
User groups
Staff get access by belonging to a group, so a new colleague has the right access in every part of the shop at once and a role is changed in one place.
A new colleague gets the right access in every part of the shop at once, and a change to what a role may do is made once, not account by account.
What it does
- Put staff in groups, such as system administrators, and their access follows in every part of the shop
- Some groups follow from who an account is, such as everyone with a verified address at the company
- Nobody can put someone in a group that gives more than they could hand on themselves
- Every account page shows which groups it belongs to and why
- Every change of membership is recorded with who made it
Why it matters
A Fusion shop is made of parts that each decide who may do what in them: accounts, returns, quote requests, customers, the CMS and more as the shop grows. Granting access part by part works for the one member of staff who needs something special, but most people's access follows from their role. A group names that role. What a group gives is decided once, for every part of the shop, and everyone in it has it. Some groups need no one to assign them: an account belongs to them because of who it is, such as everyone with a verified address at the company. What each group gives is part of the shop's own code, so a change to it is reviewed and released like any other change, and the platform cannot be released until every part has decided what each group gives there.