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.
Deactivating vs. deleting
Removing someone's access (as an admin, a group leader, or any assigned role) deactivates the relevant assignment rather than deleting the underlying user account, this preserves an audit trail of who had what access and when.
Re-adding the same person later
Reactivating a previously removed assignment for the same person and role picks back up rather than creating a duplicate record, Sermfy checks for an existing (even if inactive) assignment first.
If someone is leaving a specific responsibility but staying at the church in another capacity (a departing Branch Admin who remains a regular member), only remove the specific role assignment, don't deactivate their overall member record.
What happens immediately
Access changes take effect on their next request, permission checks run fresh on the server each time rather than relying on a cached session that could take a while to catch up.
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.
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.