Permissions
CongPlan controls what each person can see and do through permissions. An administrator sets them per user in the user editor — reachable from Congregation → Users — either by picking a ready-made role preset or by switching individual permissions on and off.
How it works
- Permissions come in two kinds: View (see something) and Edit (change it). An Edit permission normally includes the matching View, so you do not have to grant both. Three Edit permissions — Absences, Public Witnessing, and Outgoing public talks — are the exceptions: they have no View counterpart (see Good to know).
- Role presets are quick starting points (for example Elder or Editor). After applying a preset you can still fine-tune individual permissions for that person.
- The rules apply everywhere in the app: a person is only ever offered an action they are actually allowed to perform.
- Two further, narrower ways to gain edit access exist outside this permission system entirely — contextual editing and foreign-language group planners — both explained under Good to know.
What everyone can see
Every signed-in user can, by default:
- view meeting programs,
- see other publishers' names and basic data,
- view tasks,
- view field service meetings,
- view the circuit overseer visit, and
- view congregation announcements.
Anything beyond this — contact details, editing, settings, or administration — needs an additional permission.
Role presets
The Quick select in the user editor bundles common sets of permissions:
| Preset | Intended for | Grants, in short |
|---|---|---|
| Publisher | Every member | The default view access only |
| Elder | Elders | Defaults + full user details, all field service groups, and congregation settings (view) |
| Editor | Schedulers and secretaries | The Elder set + editing of meetings, users (and their absences), technical assignments, field service groups and meetings, tasks, settings, public witnessing, the circuit overseer visit, outgoing public talks, and announcements |
| Midweek planner | The midweek scheduler | Defaults + editing the midweek meeting and recording other people's absences |
| Weekend planner | The weekend scheduler | Defaults + editing the weekend meeting and outgoing public talks, and recording other people's absences |
| Admin | Administrators | Full administrator rights — everything |
After applying a preset you can still add or remove single permissions for that person.
Foreign-language groups add a further, per-group role — Group Planner — that sits entirely outside this preset list; see Foreign-language group planners below.
View permissions
| Permission | Lets the person see |
|---|---|
| Meetings | Meeting programs and parts |
| Users (names only) | Display names and basic data, without contact details |
| Users (full details) | Additionally contact details (phone, email) and permissions |
| Tasks | Tasks |
| Field Service Meetings | The field service meeting schedule |
| All Field Service Groups | Every field service group |
| Settings | Congregation settings |
| Circuit overseer visit | The circuit overseer visit |
| Announcements | Congregation announcements |
Edit permissions
Each Edit permission includes the matching View, except Absences, Public Witnessing, and Outgoing public talks, which have none.
| Permission | Lets the person |
|---|---|
| Meetings | Edit every meeting (midweek and weekend) |
| Weeks (overview) | Edit the week and overview surfaces, and special events |
| Midweek meeting | Edit the midweek (Life and Ministry) meeting |
| Weekend meeting | Edit the weekend (public talk + Watchtower Study) meeting |
| Users | Add, edit, delete, and anonymize users; sensitive actions require a passkey-confirmed session |
| Absences | Record and change other people's absences, without full user-editing rights |
| Technical Assignments | Manage technical assignments |
| Field Service Groups | Manage field service groups |
| Field Service Meetings | Manage field service meetings |
| Tasks | Create and manage tasks |
| Settings | Change congregation settings |
| Public Witnessing | Administer public witnessing plans, locations, and shifts — including signing other people up, even publishers without app access |
| Outgoing public talks | Plan outgoing public talks |
| Circuit overseer visit | Manage the circuit overseer visit |
| Announcements | Create and manage congregation announcements |
Good to know
Planning only one meeting type
The three meeting-edit permissions — Weeks (overview), Midweek meeting, and Weekend meeting — are independent. Granting one lets that person plan only that part, without giving them full meeting access. The Midweek planner and Weekend planner presets are built for exactly this.
Printing
Anyone who can edit any kind of meeting can also print the meeting-related plans, including the week and month overviews — so a planner can always produce the notices they need.
Absences: a narrow right
The Absences permission exists for planners who need to record "this person is away that week" without gaining full access to their profile. It grants write access only — there is no separate view permission — and it still requires being able to see the person at all (at least Users (names only)). Someone who already holds full Users editing, or who is the overseer/servant or assistant of the person's own field service group, can already manage absences through those paths; this permission fills the gap for a planner who holds neither. See Absences.
Circuit overseer visit: generating needs more than one permission
The Circuit overseer visit edit permission lets a person create, edit, and delete a visit. Generating or regenerating the service week additionally requires edit access to Meetings and to Field Service Meetings, because the generation run writes those rows — someone who holds only the circuit overseer permission can save a visit, but the generation step will fail. See Circuit Overseer Visit.
Contextual editing (optional)
A congregation can switch on contextual editing. When it is enabled:
- the person entered as the chairman of a meeting may edit that meeting, and
- the assigned conductor of a field service meeting may edit that meeting,
even without the corresponding Edit permission. Editing remains limited to the meeting that person is responsible for and only applies while the setting is on.
The chairman switch also has a wider privacy effect. Anyone assigned as chairman of at least one meeting can see every absence in the congregation while the switch is on. This visibility has no meeting or date restriction.
Field service group leadership
Independently of contextual editing and of the Field Service Meetings permission, a field service group's Group Overseer / Group Servant and its assistant may always create and manage the field service meetings of their own group. This does not extend to any other group, and it does not grant the group-wide Field Service Groups permission (membership, leadership, deleting the group). See Field Service Groups.
Foreign-language group planners
A congregation with foreign-language groups enabled can list per-group Planners — publishers who may plan that one group's program, without holding any congregation-wide meeting-edit permission. This is a separate mechanism from the presets and permissions on this page: a Planner's access is scoped to their group alone. See Foreign-Language Groups.
Administrators
Admin grants full administrator rights — every permission — and is required for the administrative areas such as managing congregations, history, and data import.
Full administrator rights require a passkey-confirmed current session. A login by invite, setup link, one-time code, or approved access request still allows normal planning, but an administrative page may show Confirm with passkey first. Choose Login with passkey; if no passkey exists yet, choose Set up passkey and register one under Me > Login & passkey.
This extra check applies to full administration and sensitive user master data. Normal View and Edit permissions work without a passkey. Planning work such as meetings, technical assignments, tasks, hand-overs, outgoing public talks, circuit overseer visits, and field service groups does not gain a passkey requirement merely because the person may edit it.