Campus-scoped users

A scoped user only sees data for the campus(es) assigned to them. It’s the foundation of multi-campus operation in production.

When to use scoping

Almost always. Exceptions:

• The senior pastor / administrator (org_admin).
• The treasurer (finance).
• Temporary external auditors.

Every other role should be scoped.

How to set the scope

When you invite a user or edit an existing one:

1. Settings → Team → [User] → Assignments.
2. + Add assignment.
3. Role: for example campus_admin.
4. Scope: select the specific campus.
5. Save.

To add a second campus, repeat steps 2–5. The same user can have multiple assignments.

What changes for the user

When the user signs in:

• The campus picker only shows assigned campuses.
• Global search only searches within those campuses.
• Reports only show data for those campuses.
• In Donations, they only see gifts received in their campuses.
• Members transferred to another campus disappear from their view.

What a scoped user never sees

• “All campuses” (consolidated) reports.
• Cross-campus comparisons.
• Church-wide settings (Stripe, plan, branding).
• Other users whose campus doesn’t overlap with theirs.

Example: campus pastor

{
  "name": "Carlos R.",
  "assignments": [
    { "role": "campus_admin", "scope": { "campus_id": "c_north" } }
  ]
}

Carlos can:

• ✅ See and edit North members
• ✅ See donations received at North
• ✅ Create and manage North service plans
• ✅ See the North health report

Carlos cannot:

• ❌ See Downtown members
• ❌ See the wallet or configure Stripe
• ❌ See the church-wide consolidated report
• ❌ Create new admin users