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

# Dashboard Staff Access

> Authentication and scoped choices for internal dashboard finance workflows.

These endpoints support the signed-in church dashboard. They use the staff
bearer token from dashboard sign-in and are separate from the public partner
`v1` API and its member tokens.

Requests are bound to the authenticated staff member's church. A missing or
invalid staff session returns `401`; a staff account without the required
permission returns `403`. Church administrators have access to all church
features. A permission to read choices does not grant permission to manage the
underlying records.

## Manual Gift Fund Choices

`GET /api/giving/batches/options` requires `giving_manual_entry` or the legacy
`donations` permission.

It returns only fund IDs and names available for manual gifts in the current
church. Inactive, closed, and not-yet-available funds are excluded.

```json theme={null}
{
  "success": true,
  "data": {
    "funds": [{ "id": 12, "name": "Community Food Pantry" }]
  }
}
```

## Giving Statement Member Choices

`GET /api/giving/statements/member-options` requires `giving_statements` or the
legacy `donations` permission.

It returns up to 100 current-church members, sorted by name, with only the
`id`, `name`, and `email` fields used by statement preparation.
An optional `search` string of up to 255 characters searches names and emails
across the church before applying that 100-result limit.

```json theme={null}
{
  "success": true,
  "data": [{ "id": 34, "name": "Maya Collins", "email": "maya@example.test" }]
}
```

## Member Pagination and Administration

`GET /api/members` requires `page >= 1` and accepts `per_page` between 1 and
100\. Invalid or oversized pagination parameters return `422` instead of an
unbounded directory response. The default page size remains 10.

Member directory administration, household records, profile-change review,
privacy requests, and data hygiene tools require `members` access. Those
permissions do not grant access to another church's records.

## Settings Permissions

Personal two-factor settings remain available to the signed-in account.
Church configuration requires `settings`. Payment-provider tools require
`settings`, `giving_provider_settings`, or legacy `donations` access.
Developer configuration requires `platform_integrations_manage`.

## Giving Export Filters

`GET /api/giving/export` accepts an optional `search` string of up to 255
characters alongside its date, source, and status filters. It uses the same
search rules as the giving list. Donor name and email matching require donor
detail access; other staff can search permitted references, designations, and
campaign information. Export permission is still required.

## Campus Choices for People Workflows

`GET /api/branches/options` returns only current-church branch IDs and names
for staff with `branches`, `members`, or `community_groups_manage` permission.
This supports campus selection without access to branch contacts or management
actions.

## Dashboard and Search

Dashboard summaries, recent activity, global search, and attention counts use
the staff account's feature permissions. Sensitive care and form information
also follows its record-level visibility rules. A staff account without product
permissions receives empty product summaries and results rather than another
route into restricted information.


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