Give people the access their work needs
A shared owner login makes responsibility unclear. Individual access gives a growing team a better way to work.
Name the responsibility first
Before choosing a role, describe what the person needs to do. A counter employee, a branch manager and a content editor do not necessarily need the same modules. Review branch access as well as the role label. Enabling an app for the business should not become an accidental decision to expose it to every staff member.
Review access when work changes
Permissions are not a one-time onboarding task. A person can move branches, take on a new responsibility or leave. Make access review part of those events. Ask the person to open their workspace with their own account, then check whether the available areas match the intended job. Use the proper removal flow when access is no longer needed.
Put it into practice
Use individual invitations rather than sharing an owner account. A person needs the relevant business, branch and module permissions.
- As the owner, open the team area, add or invite the person and select the intended role and branch access.
- Review the module permissions. Installing an app for the business does not automatically grant all staff access.
- Ask the invited person to accept using the intended account. Recheck access when responsibilities change or a person leaves.
Try this next
Choose one team role and write its actual responsibilities. Compare those responsibilities with the branches and modules the account can access.
June–October 2026 editorial series. Issue dates organise the series; they are not feature launch dates.