Rights in the App: Who May See What

Viewing and Editing Are Two Things

Permissions come in two kinds: seeing something and changing it. An edit permission normally includes the matching view, so you do not have to grant both. Three edit permissions are built differently on purpose and have no view counterpart at all: absences, public witnessing, and outgoing public talks. Everything is set per person in the user editor, either through a ready-made role preset or switch by switch. The rules apply everywhere in the app: an action is only ever offered where it is actually allowed.

What Everyone Sees Anyway

Every signed-in user sees meeting programs, other publishers’ names and basic data, tasks, meetings for field service, the circuit overseer visit, and congregation announcements. Anything beyond that – contact details, editing, settings, administration – needs an additional permission.

Narrow Rights for a Single Job

The rights for the midweek and the weekend meeting are independent of each other. Someone who holds only one plans exactly that part and has no full access to every meeting. The absences right is just as narrow: it exists for planners who need to record “this person is away that week” without gaining access to the profile. It grants write access only and still requires being able to see the person at all. Anyone who already holds full user editing, or who leads that person’s field service group, can manage absences through those paths anyway.

And whoever may edit meetings may also print the related plans, week and month overviews included, so a planner can always produce the notices they need.

Two Routes Outside This System

A congregation can switch on contextual editing. The person entered as chairman of a meeting may then edit that meeting, and the assigned conductor of a meeting for field service may edit that one, even without the matching edit permission. The chairman switch has a wider effect, though: while it is on, anyone assigned as chairman of at least one meeting can see every absence in the congregation, with no restriction by meeting or date.

Independently of that, a field service group’s group overseer or group servant and their assistant may always create and manage the meetings for field service of their own group, and only of their own group. And in a congregation with foreign-language groups, planners can be listed per group whose access stays scoped to that one group.

Full Administrator Rights Need a Passkey

Administrator rights cover everything and are required for areas such as managing congregations, history, and data import. They only take effect in a session confirmed with a passkey. Signing in by invite, setup link, or one-time code is enough for normal planning; an administrative page then asks for that confirmation first. Planning itself – meetings, technical assignments, tasks, hand-overs, outgoing public talks, the circuit overseer visit, field service groups – gains no passkey requirement merely because someone may edit it.