Your team: who can sign in, and what they can do

Team in the staff dashboard lists everyone who can sign in to your church, with their roles and, in a multi-campus church, their campuses. It is where you invite someone with their roles, change what they can do, and suspend or remove a login.

Invite someone with their roles

1. Open Team and choose Invite someone.
2. Enter their email address.
3. Under Roles, tick what they should be able to do once they accept: your church’s own roles first, then the built-in ones. Staff is ticked to start with. Member alone gives them the member portal only.
4. In a multi-campus church, choose their campuses under Campuses, or leave it empty for every campus. Owners and administrators always see every campus.
5. Choose Send invitation. They get an email to set up their login; the roles are theirs once they accept. Until then they show as Invited.

Someone who was removed can be invited again the same way, with new roles. To give a person in People a member portal login linked to their record, use Portal login on their record instead.

Give someone a role

1. Open Team. The Team members tab shows staff and volunteers; choose Everyone with a login to include members who only use the member portal. Search by name or email.
2. Choose the person’s name.
3. Under Roles, tick the roles they should hold: your church’s own roles first, then the built-in ones. Someone can hold more than one; they can do what any of them allows.
4. In a multi-campus church, choose their campuses under Campuses (see Staff limited to their campuses).
5. Choose Save access. It applies the next time they load a page.

Suspend or reactivate a login

Suspending stops someone signing in to your church while keeping everything about them: their roles, campuses, person record and history. Use it for a leave of absence or while something is looked into.

1. Open Team and choose the person’s name.
2. Under Sign-in, choose Suspend login, then confirm. They show as Suspended.
3. To let them back in, open them again and choose Reactivate login. Their roles and campuses are as they were.

Remove someone from the church

Removing ends their login’s place in your church: they can no longer sign in to your dashboard or member portal, and their roles here end. Their person record, giving, attendance and other history stay in People.

1. Open Team and choose the person’s name.
2. Under Sign-in, choose Remove from church. The confirmation names them and says what happens; confirm.
3. They leave the Team list. You can invite them again later.

For someone invited who has not accepted yet, the same button reads Cancel invitation: their invitation link stops working.

Good to know

• Who can do it. Owners and administrators see Team and change access. Other roles do not see it.
• Owners. Only an owner can make someone an owner, or change an owner’s roles; an administrator sees an owner’s roles but cannot change them. The church always keeps at least one owner.
• Staff access at one church per email. Giving someone a staff role, or reactivating them, is refused when their email has staff access at another church: see One email, one church’s staff access.
• Everyone needs a role. To stop someone signing in, suspend or remove them instead.
• Not yourself. You cannot suspend or remove your own login; another owner or administrator can.
• Suspending an owner. An administrator cannot suspend or remove an owner, and the church’s only owner cannot be suspended or removed: make someone else an owner first.
• API keys have a login too, and appear here as “API key”. Their roles decide what the key can do.
• Build your own roles on the Roles tab: see Custom roles.

For members

None: this is the church’s staffing.

What DCX Logic support can do

Explain what a role allows. A support session cannot invite, suspend or remove anyone: the church does that.

Coming from Planning Center

Planning Center sets each person’s access from one place, “a single interface for quickly viewing and managing a profile’s access across all the products” (Global permissions management). HoW’s Team page is that place: one dialog per person, with named roles instead of a level per product.

To stop someone’s access, Planning Center has you either set their permission level to “No access” (“they will encounter an error page the next time they try to log in”) or set their profile inactive, after which “their administrative access will be removed in every product and they can no longer log in” (Permissions in People; Inactivate or delete a profile). In HoW, Suspend login is the reversible “no access” that keeps the roles for later, and Remove from church ends the login without touching the person’s record, which stays active in People. Planning Center’s new users get an email listing “the products they’ve been given access to, their permission levels”; HoW’s invitation likewise carries the roles chosen up front.