Who runs the app, the church's clock, and the features that change how subs and sign-up work.
In the app: Settings → Admins, features and time zone
Admins
The people who can change settings, approve any block and see everything. Changes apply at once. There's always at least one.
- Default
- config.yaml's admins
- Values
- people on the roster
- Example
- The children's pastor and the ministry coordinator.
Treat missing training dates as current
Someone with no training date in Planning Center can still be scheduled (useful while the dates are being entered).
- Default
- off
- Values
- on or off
- Example
- On for the first month, while the office enters everyone's dates.
Fix now
On the discrepancies page, "Fix now" changes Planning Center (adds someone to a position, corrects a name), as the admin who clicks.
- Default
- on for a new church (#942), with a warning before it's turned off; off where the church runs from config.yaml
- Values
- on or off
- Example
- Off until the admins have tried it together once.
- Planning Center needs
- Editor in Services (with people assignments allowed), Editor in People for names
Coordinator's GitHub username
Mentioned in the schedule-health issues the nightly check files (single-church setups that use GitHub).
- Default
- none
- Values
- a GitHub username
- Example
- kids-coordinator.
Time zone
The church's clock everywhere. "Today", arrival times, reminders, the daily jobs and every date and time the app shows are in it, so a leader travelling sees the same Sunday as everyone else.
- Default
- America/New_York
- Values
- a time zone like America/Chicago
- Example
- America/Denver, for a church in Colorado; at 11pm Saturday there it's still Saturday in the app.
Date format
How the app writes dates, such as "Oct 18" on the schedule and "Until Oct 2028" for training. Arkrooms is for US churches for now, so US dates are the only choice; another country's format comes when that country opens.
- Default
- en-US
- Values
- en-US
- Example
- en-US, so a Sunday reads "Sunday, Oct 18".
A leader approves every sub
When someone offers to sub, a leader of the team approves before they're on the schedule.
- Default
- on
- Values
- on or off
- Example
- On, so leaders know who's in their rooms.
A sub is a trade
Whoever covers a Sunday gives one of theirs back, so everyone's share stays even.
- Default
- off
- Values
- on or off
- Example
- On, for a team that likes things even.
Sub requests can go to the requester's own team
Off, a sub request goes to the neighboring teams and then every other team, never the requester's own, which is serving that Sunday. A church with one team always asks it. Shown when the church has more than one team.
- Default
- off
- Values
- on or off
- Example
- Off, for a church whose teams rotate.
Volunteers sign themselves up
Off (leaders make the schedule), the empty places of a schedule, or a whole block before it's scheduled. Leaders open each block for sign-up.
- Default
- off
- Values
- off, gaps, block
- Example
- Gaps, so volunteers fill the holes and a leader approves each.
Photos on the room map
The room map shows each volunteer's Planning Center profile photo in their circle instead of their initials, to everyone who can see the map. Anyone can hide their own photo on My choices. Photos are shown live from Planning Center and never stored.
- Default
- off
- Values
- on or off
- Example
- Off, unless your church already shares photos in its directory.
Keep me signed in on this device
Volunteers and leaders can choose to stay signed in on their phone or computer for 30 days. Admins always sign in again.
- Default
- on
- Values
- on or off
- Example
- On.