Understanding Roles and Permissions
The basic model behind Sermfy access, default roles, and how branch scoping works.
The basic model
Every user is assigned one or more roles, and each role carries a set of permissions, individual permissions aren't assigned directly to a person, they always flow through a role, which keeps access consistent and easy to audit.
Default roles
Sermfy ships with baseline roles like Super Admin and Admin (renamed from an earlier "Pastor" role at the branch level), additional roles can be created to match how your church actually organizes responsibility.
A role can be scoped to a specific branch for multi-branch churches, so an Admin role assigned at one branch doesn't automatically grant access to another branch's data.
Where permissions are enforced
Permission checks happen on the server, not just by hiding a button in the interface, so access is enforced consistently even if someone tries to reach a page directly.
Related Articles
Managing Multiple Branch Admins
Assign more than one admin per branch, and what happens when an email is already linked to a login.
Deactivating or Removing a User's Access
Why removing access deactivates rather than deletes, and what happens if you re-add the same person later.
How Permission Checks Work Behind the Scenes
Why access is enforced on the server, and how branch scoping factors into every check.
Creating a Custom Role
Build a role scoped to exactly the permissions your church's structure needs.