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.