Edmissa docs

Users, roles, and permissions

Understand how user accounts, roles, permissions, scope, locations, and supervisors work together.

Users, roles, and permissions control who can sign in to Edmissa, which records they can work with, and which settings they can change.

Use this page as the access-control overview. Then open the focused guide for the part you are configuring.

How the pieces fit together

PieceWhat it controls
UserThe account that signs in to Edmissa.
RoleA reusable permission set assigned to one or more users.
PermissionThe action or setting the role allows.
Access levelWhether the role can view, manage, or fully control a data area.
ScopeWhich records the access level applies to: own, assigned, team, or all.
LocationWhich branch or operating location the user belongs to.
SupervisorThe reporting relationship used for team visibility and manager review.

A user usually needs three things before daily work is reliable: an active account, at least one role, and at least one location.

  1. Create or confirm the locations your agency uses.
  2. Create the roles that match real job responsibilities.
  3. Review each role's permissions and scope before assigning it.
  4. Create users and assign the right roles and locations.
  5. Add supervisors when your agency needs manager visibility.
  6. Test one sample user from each role before inviting the full team.

Start narrow. It is easier to expand a role than to remove broad access after users have started relying on it.

GuideUse it for
UsersAdd users and manage account access.
User Location AssignmentsAssign users to branches or operating locations.
RolesBuild permission sets for job responsibilities.
Permissions and scopeUnderstand how Edmissa decides what a user can see and do.
LocationsConfigure branches and location assignments.
Security and auditReview password, session, audit, and security settings.
Access and permissions troubleshootingDiagnose missing pages, disabled actions, and record visibility issues.