Representation
Representation lets a person help another person with a small set of planning tasks. The direction is always A represents B: A is the representative and B is the represented person. One representative can represent up to two people. It is intended especially for people who do not use the app themselves.
Representation is not a general account permission. CongPlan checks that the relationship is active and belongs to the same congregation whenever an action is requested. After an expiry, revocation, missing permission, offline replay, or a server rejection, an unavailable action is not a successful action.
Set up representation
An administrator manages representation on the profile of A, the representative. There, the administrator can add B, record the required consent, set an optional expiry date, and see A's quota of up to two represented people. The same place is used to revoke a relationship.
This setup does not belong on B's profile: B is the person being represented, while A is the person whose quota, consent, expiry, and revocation are managed. The status shown in each person's own area only explains an existing active relationship; it does not replace the administrator's setup or revocation controls.
See representation in your own area
The profile-status portion of representation is delivered separately. Until then, the existing setup and local actions remain unchanged. When it is available in your CongPlan version, both people can recognise an active relationship in their own profile area. A can see the people A currently represents. B can see who represents B. Where an expiry date has been set, the status also shows its duration or end date.
This is a status and entry point, not a way to become another person. It does not switch accounts, create a global person mode, or give A a general view of B's profile. B's status explains that A can only use the local actions described below. Administrative setup, the quota, consent, and revocation remain on A's profile for authorised administrators.
Use the permitted local actions
When an active relationship and the required local permission allow it, A can choose an action for B in exactly these places:
- sign B up for, or withdraw B from, a public-witnessing shift;
- record the location of a field-service meeting for which B is authorised; and
- manage B's absences.
The choice stays at the relevant action. It is not a global switch and does not change A's session. Buttons, confirmations, and messages identify B so that a change is not mistaken for A's own change.
Representation does not let A imitate B, take over B's account, or browse
B's settings, contacts, reports, inbox, or other data. A failed authorisation,
an expired or revoked relationship, a 403, 404, or 422 response, or a
rejected offline replay never means that representation is still available.
Read the plan and cards
Assignments for B can appear alongside A's own assignments in A's personal plan and on the relevant cards. An event stays a single card: when it contains both people's assignments, the affected line identifies B with a name and a representation marker. The marker is not based on colour alone and does not mean that A has changed accounts.
Only the assignment or local action that concerns B is marked. B's absences do not become foreign plan or card content. If the active relationship ends, the represented entries and actions disappear on the next refresh; cached or failed requests must not be read as proof of an ongoing permission.