Managing Multiple Branch Admins
Assign more than one admin per branch, and what happens when an email is already linked to a login.
Why more than one
Larger branches often need more than a single admin, Sermfy supports assigning multiple people to an admin role at the same branch, each with the same level of access rather than one "primary" admin and lesser helpers.
Adding an admin
From a Branch's details, then Admins, pick a member and a role to assign, scoped to that specific branch. If the member doesn't yet have a login, Sermfy creates one and shows a one-time credentials screen.
If the member's email already has a Sermfy login (for example, reusing an account for testing), Sermfy links the existing account instead of creating a conflicting duplicate.
Removing an admin
Removing an admin deactivates their access to that branch rather than deleting their account entirely, their user record and any audit history remain intact, and they can be reactivated later without losing that history.
Related Articles
Understanding Roles and Permissions
The basic model behind Sermfy access, default roles, and how branch scoping works.
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.