> ## Documentation Index
> Fetch the complete documentation index at: https://docs.faithloft.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage your church organization

> Review branches and roll-up reporting, create branches, push shared setup, and transfer members.

Use **Organization** to see the branches in your church network and, when your role allows it, manage shared setup and move members between branches. You need organization reporting access to open this area. Management actions require additional access; contact your church administrator if a page or action is unavailable.

If your organization has sub-branches, expand **Organization** in the portal menu to see **Overview**, **Branches**, **Roll-up**, **Members**, **Departments**, **Roles**, **Events**, **Transfers**, and **Activity**. The cross-branch directory pages are shown only when your organization has sub-branches.

## Review the organization tree

1. Open **Organization** and select **Overview**.
2. Review the totals for branches, members, departments, and reporting coverage.
3. Switch between **Grid** and **Tree** under **Branch health**. Select a branch to see its location in the hierarchy, its status, and available metrics.
4. Use the **Open portal** link on a live branch when you need to open that branch's portal.

The selected branch's status helps you see whether it is active or needs attention. A branch with no report displays dashes for unreported metrics; those dashes do not mean the value is zero. Use **Roll-up** to compare reporting coverage and totals across branches, including the report timestamp.

## Create a branch

Create a branch when a church or campus should have its own portal under the organization.

1. From **Overview** or **Branches**, select **New branch**. To create below a specific branch, select that branch and choose **Add sub-branch**.
2. Choose the **Parent branch**. Leave it set to **Under my organisation** to create directly under your organization.
3. Enter the branch **Name**. The **Subdomain** is suggested from the name; edit it if needed. It must use lowercase letters, digits, and hyphens, and start with a letter.
4. Enter the **Admin email** and optionally the **Admin name**.
5. Select **Create branch**.

Branch provisioning happens in the background. Return to **Branches** to check its status. If it remains pending or failed, contact your church administrator before trying to create a duplicate.

In **Branches**, search by branch name or subdomain, filter **All**, **Active**, or **Needs attention**, and select a branch to open its inspector. Branch actions can include **Heal** for a branch that is still provisioning or has failed.

## Push shared setup to sub-branches

You can queue shared setup for all sub-branches or for the subtree beneath a selected branch.

1. Select **Push setup** for the organization, or select a branch and choose **Push to this subtree**.
2. Under **What to push**, choose **Branding**, **Department templates**, and/or **Module defaults**.
3. Choose a **Mode**: **Use defaults**, **Fill missing**, or **Overwrite**.
4. Review the target scope in the dialog, then select **Push setup**.

The setup push is queued to the descendant branches in that scope. Review the target and mode carefully, especially before using **Overwrite**. A selected branch with no sub-branches has no recipients.

## Transfer a member between branches

A transfer moves the member's identity and profile to the destination branch. Department roles do not carry over, and the source login is closed.

1. Select **Transfer** from **Overview**, or **Transfer a member** from a branch inspector. You can also start from a member in the organization-wide **Members** list.
2. Choose the **From branch** and **To branch**. When you start from a member's row, the source branch and member are already selected.
3. If needed, enter the **Member email**.
4. Confirm the source and destination, then select **Transfer member**.
5. Open **Transfers** to follow the request. Its status may be **Pending**, **In progress**, **Done**, **Failed**, or **Cancelled**.

Only active or ready branches can be used in a transfer. Make sure the destination church is prepared to assign any department roles the member needs after the move.

## Use the cross-branch directories

When available in the **Organization** menu:

* **Members** lists members across branches. Search by name or email, filter by status or branch, and review each member's church, role, and last login. Depending on your access, actions may include suspension, reactivation, or transfer.
* **Departments** lists branch departments. Search by name or slug, filter **Live** or **Draft**, and review visibility and membership counts. Authorized staff can publish or unpublish a department.
* **Roles** compares role names, system status, permission counts, and member counts by church.
* **Events** compares attendance sessions in the last 30 days, active memberships, and upcoming events by church.
* **Transfers** lists transfer requests. Use the status filter to find requests that are in progress or need attention.
* **Activity** shows hierarchy-level actions, the actor and target branch, result, and time.

These pages are reporting and management views across churches. To manage a single department, member, or event in its home portal, open that branch's portal and use the relevant module. For general navigation, see [Web portal modules](/portal/modules).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.