Manage communities in a pastoral unit

Open Settings > “Your parishes & PU”. “The communities you manage.” shows “Operating as …”, the number of associated communities, pending requests and any available pastoral unit.

Below the community list, “Pastoral Units” identifies each unit by name, member count and mode. Do not use edit until you have checked whether the row says “Bulk Operations” or “Merged”: the modes have different effects.

On a “Bulk Operations” row, select “Operate as”; on a “Merged” row, select “Operate as this one”. When the unit is already active, the row says “Currently operating” and the heading changes to “Operating as [name]”.

If the control says “Activate to operate”, the unit exists but the required access is not active, so the remaining workflow is unavailable. Return to a single-community context until pastoral-unit access is available.

Functions that keep per-community data show “Select parish”. Choose the correct member and read the note below: “What you create here stays in this parish” identifies a local operation.

Other pages in bulk mode can state that new content will be published to all communities in the unit. The page note is decisive; do not infer scope from the name in the heading alone.

For a “Bulk Operations” row, use the pencil button. In “Edit Pastoral Unit”, update name and description, select Next, then choose communities from the list; search appears when the list is long.

You can save only with at least two manageable communities selected. Membership uses the «Manage places and celebrations» permission; do not treat a community you cannot manage or one already assigned to another unit as available.

A “Merged” row also shows “Visible” or “not public”, follower count and places of worship. Select “Edit” to open settings for the merged identity; the interface activates that unit first and then opens Identity.

The visibility pill changes whether the unit is public. If a strip reports content “still to import into the PU”, use “Import” only after reviewing what should move into the merged identity: importing is separate from simply changing context.

Return to “The communities you manage.” and check the name in “Operating as …”. On the unit row, verify community count, mode and “Currently operating” before opening another function.

Open a function with the switcher and confirm the active community. For a local change, verify the data inside that member; for a merged-identity change, return to the unit context and use its public preview.