Users, Roles & Access
Invite your team and control who can see and change what, with roles and permissions.
- ArticleHow access works: user, role, permissionAccess in Sonta is a short chain: a user belongs to a role, and the role carries a set of permissions. You don't grant abilities one at a time — you give a person a role, and the role decides what they can do. Roles and permissions live inside one business and never cross to another.
- ArticleInvite a userDecide which role the person should have, then send them an invitation by email. They become a member with that role's permissions once they accept the emailed link — until then they have no access. Invitations can be resent or cancelled while pending.
- ArticleDesign a role: what permissions governPermissions are grouped by what they govern: the business itself, the structure of your collections, the records inside them, the stages work moves through, and invitations. The most useful line to draw is between changing the structure and working with records — and one permission decides whether a person sees every record or only the ones assigned to them.
- ArticleCreate a custom roleCreate a custom role by giving it a name that is unique in the business, ticking the permissions it should carry, and adding people to it. The built-in Admin role cannot be changed, so any narrower set of abilities needs a role of your own.
- ArticleChange a user's roleTo change what a person can do, add them to the new role and remove them from the old one. The change applies at once, to them and to any agent connected as them. Only an administrator can take someone out of the Admin role, and the last administrator cannot be removed.
- ArticleManage access across businessesAccess is granted one business at a time. To give someone access to a second business, invite them to it and give them a role there; their role in one business says nothing about another. People and agents then switch between their businesses, and the one they last selected is remembered.
- ArticleWho sees which entriesIn a collection with an owner field, people see the entries they own plus the entries no one owns, unless their role allows seeing every entry. Collections without an owner field are visible in full to everyone who can open them. The table opens on your own entries by default, which is a view choice, not a limit.