Creating a Custom Role
Build a role scoped to exactly the permissions your church's structure needs.
When to create one
If your church's structure doesn't map cleanly onto the default roles, say, a "Finance Officer" who should see Finance but nothing else, create a custom role rather than stretching an existing one's permissions.
Building the permission set
From Users & Roles, then Roles, create a new role and select exactly which permissions it should carry, module by module, Members, Groups, Finance, Communication, and so on.
Start narrower than you think you need. It's straightforward to add a permission to a role later; it's a bigger conversation to realize a role has been over-permissioned for a while.
Assigning the role
Once created, assign the role to specific users the same way you would any built-in role, from that user's account or from the Branch Admins screen if it's branch-scoped.
Related Articles
Understanding Roles and Permissions
The basic model behind Sermfy access, default roles, and how branch scoping works.
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.