Each service on a Sunday, when it starts and how long it lasts, when volunteers arrive, and the age groups (rooms) it has. These per-service settings repeat for each service.
In the app: Settings → Services
Name
The service's name as volunteers see it.
- Default
- from config.yaml
- Values
- text
- Example
- Second Service.
Starts
When the service starts. Volunteers' arrival time is worked out from it (Volunteers arrive … minutes before).
- Default
- from config.yaml
- Values
- a time like 10:00am
- Example
- 10:00am.
Minutes long
How long the service lasts. Calendar entries run from arrival to the service's end.
- Default
- 75
- Values
- 15 to 300
- Example
- 90, for a service from 10:00 to 11:30.
Volunteers arrive … minutes early
How long before the start volunteers should be in their room. One number for every service, or a service's own under More. Reminders, My schedule, the live window on Sunday, the welcome on check-in and calendar entries use the arrival time.
- Default
- 15
- Values
- 0 to 120
- Example
- 15, so volunteers arrive at 9:45 for a 10:00 service.
Arrive by
When volunteers should be in their room, worked out from the start and the minutes before. Shown on the Settings page; not set directly.
- Default
- the start minus the minutes before
- Values
- a time like 9:45am
- Example
- 9:45am, for a 10:00 service.
Age groups
The rooms (age groups) this service has. Each becomes a place on the schedule, and is mapped to a room on the floor plan and a Check-Ins location on the Rooms page.
- Default
- from config.yaml
- Values
- age-group labels like 0-1, 2-3, K-2
- Example
- 0-1, 1-2, 2-3, 3-4, 5-6, 7-8.
Main service
The service backups belong to, and the one "serves the main service once" counts (Rules).
- Default
- the first service
- Values
- one service
- Example
- The 10:00 worship service.