For Churches

Oaks access architecture

Church Partner is an organization status. People move through scoped roles: Volunteer, Church Steward, Church Admin, and Oaks Admin.

Start a Partnership View Authorization Map

Person Roles

A clear ladder from public visitor to global admin

These are person permissions. They are separate from the church's organization status, so a Church Partner can have volunteers, stewards, and church admins without making every person an admin.

Visitor

Public website

Anyone browsing Oaks without signing in. They can read public pages, explore partnership, and start public forms.

Read public pages and resources
Submit public interest forms
Create an account when ready

Member

Signed-in individual

A free Oaks account. Member access is personal and does not make a church a partner.

Use the Volunteer Account shell
Save identity/profile details
Connect to a church when credentials are provided

Volunteer

One partner church

A person connected to one Church Partner. Volunteers can access training and resources assigned to that church.

Belongs to one church
Accesses church-assigned training
Can be promoted by a Church Admin

Church Steward

Assigned groups only

A trusted group-level leader. Steward access is intentionally narrow: assigned groups, assigned people, and assigned results.

Sees only assigned church groups
Helps coordinate group volunteers
Cannot manage whole-church access

Church Admin

One church

The church-side authority between Church Steward and Oaks Admin. Church Admin manages people, groups, leaders, and future church-level results for their church.

Invites volunteers
Promotes active volunteers to Church Steward
Manages church groups and group leaders
Views future church-level questionnaire results

Oaks Admin

All churches

The global Oaks authority. Oaks Admin controls churches, content, access, groups, and platform settings across the whole network.

Manages all churches and access
Publishes content and training
Controls groups and global settings

Organization Status

Church Partner is not a person permission tier.

Church Partner describes the church account: its partnership standing, subscription package, public directory visibility, and join credentials. Person access is handled separately through church-scoped memberships.

Church Partner

Org status

Owned by: Church account
Stored as: churches + subscription records
Unlocks: Church training and tools
Does not mean: Every person is an admin

Church Admin

The church-side authority tier

Church Admin sits between Church Steward and Oaks Admin. It manages one church, not the whole Oaks network.

Church scope

Invite Volunteers

Church Admin sends the path for an active person to join the church as a Volunteer.

Role action

Promote Stewards

Active Volunteers can be promoted instantly into Church Steward access for specific group work.

Church scope

Manage Groups

Groups are owned by one church and can be created, renamed, and organized by Church Admin.

Group scope

Assign Leaders

Church Stewards are assigned to specific groups through group leader records.

Future spec

Questionnaire Results

Future results will be scoped by church and group, with Steward access limited to assignments.

Supabase Visual Spec

Authorization map for the later live implementation

This is a visual product specification only. It does not deploy schema changes, RLS policies, or live Supabase integrations.

TablePurposeRule

profiles

Identity and global Oaks admin flag

Stores the signed-in person and whether they are an Oaks Admin.

church_memberships

Church-scoped person roles

Stores Volunteer, Church Steward, and Church Admin assignments for one church.

church_groups

Groups owned by a church

Every group belongs to a church, not to the global account by default.

group_leaders

Steward-to-group assignments

Limits Church Steward visibility to only assigned groups.

questionnaire_results

Future result visibility

Results are scoped by church and, when applicable, by group.

Rule Model

The access rules the UI should make obvious

Each role is scoped to the smallest useful authority boundary.

1Volunteer belongs to one church.
2Church Admin can promote active volunteers to Church Steward instantly.
3Church Steward sees assigned groups only.
4Church Admin sees and manages their church.
5Oaks Admin sees and manages all churches, content, access, groups, and global settings.

Visibility Matrix

Who sees what

Surface	Volunteer	Steward	Church Admin	Oaks Admin
Public pages	Yes	Yes	Yes	Yes
Volunteer training	Own church	Own church	Own church	All churches
Group people and results	No	Assigned groups	Own church	All churches
Group creation and leaders	No	No	Own church	All churches
Content and global settings	No	No	No	Global