CRUD: Church Settings and Profile
starter-chat
Persona: pastor-admin
Touchpoint: /admin/[token]/settings-tab
Preconditions
- Pastor logged into admin dashboard
- Has admin or owner role
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Navigate to Settings tab | Settings tab loads. Shows sub-tabs: Church Profile, Billing, Team Members. |
| 2 | Edit church profile (name, denomination, size) | Form fields populate with current data. Can edit church name, denomination, size. Changes save and reflect in dashboard. |
| 3 | Upload church logo | Logo upload accepts image files. Preview shows new logo. Takes effect on public pages. |
| 4 | Update church website URL | Can input/edit website URL. Used for chatbot knowledge base and integrations. |
| 5 | Set timezone for church | Dropdown to select timezone. Used for scheduling, reporting, and voice agent hours. |
| 6 | View billing information | Billing sub-tab shows current plan, renewal date, payment method. Easy to read summary. |
| 7 | Update payment method | Can add/change credit card. Secure form. Shows last 4 digits of stored card. |
| 8 | Manage team members | Team sub-tab shows list of invited admins/staff. Can add new member (email), set role (admin, staff, viewer), remove members. |
| 9 | Change user role | Can promote staff to admin or demote admin to staff. Changes take effect immediately. |
| 10 | Remove team member | Can delete team member. Confirmation prevents accidental removal. Once removed, member loses access. |
Known Failure Modes
- Logo not uploading — branding inconsistent
- Timezone not saving — reporting times are off
- Team member changes not taking effect — permissions still old
- Billing info not accessible — pastor confused about renewal date
References
- Playwright spec:
e2e/crud-admin-settings.spec.ts - Code files:
Notes
Tests church profile, billing, and team management. Settings are foundational — incorrect church data confuses the AI, wrong timezone breaks reporting, and team access issues block collaboration. All changes must save immediately and be reflected across the dashboard.