← All guides

Tenant settings walkthrough

Tenant settings are the ecclesia-wide knobs an administrator turns to shape how the scheduler behaves and what members see. Most defaults are sensible; this guide walks each card so you know what a change actually affects. Reading time: seven minutes.

Open the Settings page

Open Manage in the top navigation, then Settings in the Administrator section of the rail (Branding sits just below it). The Settings page is a stack of cards; each covers one concern. Changes save when you click Save settings at the bottom — the form is atomic so partial saves aren’t possible.

The Settings page showing a stacked list of cards, each covering one concern (Reminders, Defaults, Directory visibility, and more). The Manage rail on the left lists the Administrator section's Settings and Branding among others.
The Settings page showing a stacked list of cards, each covering one concern (Reminders, Defaults, Directory visibility, and more). The Manage rail on the left lists the Administrator section's Settings and Branding among others.

Reminders: when the scheduler emails members

Each row in the Reminders card is a “send X days before the occurrence” cadence. Add multiple rows if you want a two-touch schedule (e.g. one at 7 days, one at 1 day). Setting zero rows disables the reminder pipeline entirely.

A per-member override is planned so individual actors can opt in to a personal cadence or out entirely. Until it lands, this card is the policy.

The Reminders card showing one row: 'Days before' input set to 7, with an X remove icon. Below is an Add reminder button.
The Reminders card showing one row: 'Days before' input set to 7, with an X remove icon. Below is an Add reminder button.

Defaults and roster policy

The Defaults card’s New members willing by default checkbox decides what a new member’s preferences look like on day one. Ticked (the recommended default) means the solver considers them for every role they’re eligible for; unticked means they see a blank preference sheet and have to opt into each role.

A separate Roster policy card carries Allow members with unspecified sex in sex-restricted roles. Off (the safer default) means a member whose sex isn’t recorded is ineligible for sex-restricted roles — they can fill their profile or ask an administrator to.

The Defaults card with a 'New members willing by default' checkbox. A separate Roster policy card carries an 'Allow members with unspecified sex in sex-restricted roles' checkbox.
The Defaults card with a 'New members willing by default' checkbox. A separate Roster policy card carries an 'Allow members with unspecified sex in sex-restricted roles' checkbox.

Directory visibility: who sees what on the members list

Two visibility ladders control what tiers of member see on the Members directory:

  • Household detail — who can click through from the directory to a family’s page. The household name always shows in the table; this gates the link, not the column. Defaults to All members.
  • Postal address column — whether the address column shows, and to whom. Defaults to Administrators only because addresses are the most sensitive field on the directory.

Both use the same four-tier ladder: All members, Coordinators + admins, Administrators only, Nobody (hides it entirely).

The Directory visibility card with two select fields: 'Household detail' set to 'All members' and 'Postal address column' set to 'Administrators only'. A note beneath explains that the address column defaults to admin-only to protect residential addresses from a full-tenant leak.
The Directory visibility card with two select fields: 'Household detail' set to 'All members' and 'Postal address column' set to 'Administrators only'. A note beneath explains that the address column defaults to admin-only to protect residential addresses from a full-tenant leak.

Admin impersonation and member self-edit

Admin impersonation lets administrators sign in as any member to investigate a bug or set something up on their behalf. Every impersonation event is audited. Some ecclesias prefer this off; the default is on for support convenience.

Member self-service lets members edit their own sex after their 7-day onboarding window. Off is the safer default because sex changes affect scheduler behaviour against sex-restricted roles.

The Admin impersonation card with a checkbox 'Allow admins to impersonate members', and a Member self-service card with a checkbox 'Let members edit their own sex after onboarding'. Both cards note the safer default and the audit trail.
The Admin impersonation card with a checkbox 'Allow admins to impersonate members', and a Member self-service card with a checkbox 'Let members edit their own sex after onboarding'. Both cards note the safer default and the audit trail.

Sign-in options live under Security

How members sign in lives on its own Security page (Manage → Security in the side rail), separate from the scheduler settings above.

Sign in with Google is off by default — enable it if your ecclesia wants members to use a Google account rather than a password. The allowed-domains list restricts which Google accounts are accepted (empty means “any Google account that matches a member email”; a list restricts to accounts under those domains). A member still needs an existing tenant record with a matching email; the OAuth flow only replaces the password step, not the member-of-tenant check.

Passkeys (also off by default) let members sign in with Face ID, Touch ID, or a security key. A passkey counts as multi-factor on its own, so there’s no separate code step. It’s a per-tenant opt-in; the member-facing sign-in experience is rolling out.

The Security subpage under Manage, showing a Passkeys card with an 'Enable passkey sign-in' checkbox and a Sign in with Google card with an Enabled toggle and an Allowed email domains textarea.
The Security subpage under Manage, showing a Passkeys card with an 'Enable passkey sign-in' checkbox and a Sign in with Google card with an Enabled toggle and an Allowed email domains textarea.

Save and verify

Click Save settings. A toast confirms the save; the audit log records who changed which fields. Some changes (reminder cadence, directory visibility) take effect immediately; others (default willingness on new members) apply to future member invitations only.

The bottom of the Tenant settings page showing a Save settings button. Above it a small alert: 'Saved. Members will see the new reminder cadence starting from the next scheduled reminder run.'
The bottom of the Tenant settings page showing a Save settings button. Above it a small alert: 'Saved. Members will see the new reminder cadence starting from the next scheduled reminder run.'

On the iPhone app

Toggle the feature switches from the app's admin Manage hub.

  1. Manage → Tenant settings has two grouped toggle sections: Features (Sunday School, Congregational attendance, Parents see child attendance, Live quizzes, Duty forms) and Access (Passkeys, Allow admin impersonation).

    Manage → Tenant settings: Features and Access toggle groups.
    Manage → Tenant settings: Features and Access toggle groups.

On the web only: The rest — roster horizons, email theme, reminder cadence — stays on the web. (Swap approval is a per-role setting in the Roster-role editor, not a tenant toggle.)

What next?

  • Roster cycles covers the Roster cycle defaults card in more detail.
  • Branding — reached from the Branding item in the Manage side rail — is where tenant name, logo, timezone, and primary colour live, separate from these settings on purpose.
  • Every settings change is on the Audit page with actor + field names — useful for “who turned off impersonation and when?”.