Getting Started, Part 2: Adding Your Team and Assigning Roles

Step 1: Understand roles before assigning them

Every user's access flows through a role, not individual permission toggles (see Understanding Roles and Permissions), decide roughly what roles your team needs (Admin, Branch Admin, Finance Officer, Group Leader) before assigning anyone.

Step 2: Add Branch Admins

For each branch, assign at least one admin (see Managing Multiple Branch Admins), if the person doesn't have a login yet, Sermfy creates one and shows you a one-time credentials screen to share with them securely.

Step 3: Create custom roles if the defaults don't fit

If your church has a role that doesn't map to a default (a dedicated Finance Officer, for example), build a custom role scoped to just what they need (see Creating a Custom Role) rather than giving them a broader default role.

Share one-time credentials securely (in person or a private message), not over an unsecured channel, they grant real access to your church's account the moment they're used.

Best practice

Start every new team member with a narrower role than you think they need, it's a quick follow-up to add a permission later, but walking back over-broad access after the fact is a bigger conversation.