MiaChiesa
IT
Tutorial · Configuration and staff

Manage pastoral-unit workspace context

Move between a single-community workspace and a pastoral unit, recognize the current context and verify where a switch takes you.

6 minVerified on 21 Sept 2026Leaders and office staffOperating in the unit requires active Pastoral Unit add-on accessAvailable on activation
Download PDF
Step 1 of 5
In this guide
Start
1Step 1 of 5 · 1 min

Check the current context

In the sidebar or mobile header, the community control shows the entity currently in use. When it shows the pastoral-unit name, staff pages resolve data and permissions in that context; when it shows a member community, you are working in single mode.

This control changes the whole workspace. It differs from the Data of selector inside some pages, which changes only the member community being viewed.

Fig. 1The name in the community control identifies the operating context used by staff navigation.
2Step 2 of 5 · 1 min

Open Switch community

Select the control bearing the current name. Switch community first shows You are viewing, followed by available communities. A pastoral-unit row has the network icon; staff assignments are marked on entities where you can open the workspace.

When there are at least six entries, Search for a community or group appears. Search filters names but does not alter permissions or entity status.

Fig. 2The dialog exposes the current context and available destinations; no row is selected in the capture, so the context remains unchanged.
3Step 3 of 5 · 2 min

Enter the unit or return to a community

Select the pastoral-unit row to enter its workspace. After switching, MiaChiesa closes the dialog, returns to the dashboard root and remembers the unit and mode for later navigation. The previous active member is cleared, and pages that need one choose a valid member.

To leave, reopen Switch community and select a community where you hold a staff assignment. MiaChiesa returns to single mode, clears the saved unit and member, and opens the selected community’s dashboard.

Fig. 3For comparison, the dialog is open from single mode: it shows the current community and available unit, but no row is selected in the capture.
4Step 4 of 5 · 1 min

Handle inactive access and automatic selection

If the chosen unit lacks active operating access, the flow may send you to Plan or show Pastoral Unit not active with Reactivate the subscription. The structure is preserved, while changes that require the add-on remain blocked.

A collaborator who works only through a Merged unit may be placed in that context automatically at sign-in. A Bulk Operations unit is restored automatically only when add-on access is available and the collaborator has at least two valid communities in the unit.

5Step 5 of 5 · 1 min

Verify after switching

After a real selection, check the name in the sidebar or header. Open a staff page and verify the displayed mode and any member-community selector before creating content.

If the name does not change or an error appears, reopen the switcher and retry. Do not continue editing until the control shows the expected context.

What you have achieved

  • The header control shows the intended operating context.
  • The whole-workspace switch is clearly separated from member selection inside a feature.

Troubleshooting

The pastoral unit is missing

Verify that you hold an assignment or permission to discover it and that it is linked to your account. The switcher does not add unavailable entities.

Selecting it opens Plan

Operating access to the add-on is inactive. Review the plan and reactivate Pastoral Unit before retrying.

I am in the unit but a page shows one community

Some features retain member-owned data. Read the page’s internal selector and its write-scope pill.