> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/brains/settings.md).

# Settings and ownership

Open a Brain's **Settings** tab to manage its name, audience, refresh schedule, GitHub export and lifecycle. Available actions depend on current Brain permissions, not merely your organization role.

## Edit general settings and sharing

1. Open **General**, change the name or description, and select **Save changes**.
2. Review the saved result before leaving the sheet.
3. For a Team Brain, open **Sharing** to manage users or groups and their **Viewer** or **Editor** grants. Managing sharing requires current management and sharing-roster permission.
4. Review the complete audience and save the changes.

**Kind** is fixed: Personal and Team Brains cannot be converted into each other. A Personal Brain has no audience grants; a Team Brain with no grants is owner-only. Adding an Editor provides contribution access, not ownership.

Brain sharing and source-document sharing are different. Additional document viewers do not gain Wiki or fact access. Removing a Brain audience grant does not necessarily remove a separate document grant. Review [Sources](https://docs.katara.ai/about/brains/sources.md) when changing someone's access across both surfaces.

## Set a refresh schedule

Open **Refresh schedule**, enter a supported five-field UTC cron expression or supported standard calendar alias, then select **Save changes**. Leave the schedule empty to turn scheduled refresh off. The editor validates changed schedules; follow its error rather than assuming every cron dialect is supported.

A refresh schedule concerns local knowledge maintenance. It is not the separate [GitHub export schedule](https://docs.katara.ai/about/brains/github-export.md). Use [Activity](https://docs.katara.ai/about/brains/activity.md) to check actual refresh outcomes instead of treating a saved schedule as a completed run.

## Handle concurrent changes

Settings saves check the revision you opened. If someone else changes the Brain first, reload the current settings and explicitly reapply your intended edits after comparing them. Do not repeatedly submit an old draft or assume a conflict was automatically merged.

If access changes while a sheet is open, protected controls may disappear. Reopen only after current authority is confirmed; old visible data does not grant continuing permission.

## Transfer or recover ownership

> The newer ownership-transition controls depend on matching frontend, SDK and backend prerequisite-read support. If eligibility cannot be checked in your environment, ask your administrator to confirm that support; do not bypass the check or infer eligibility from organization rank.

For an eligible **Team** Brain, its current owner can choose **Transfer ownership**, select an authorized organization member, then choose **Check eligibility → Confirm transfer**. The member selector may show member identifiers rather than names; verify the intended person before confirming. A fresh server check must validate ownership and membership.

Recovery is separate organization-owner governance for a **known orphaned Team Brain**. Where offered, **Recover Brain ownership → Check eligibility → Confirm recovery** recovers it to the acting organization owner's account. The server requires committed removal of the former owner and their current absence; inactivity or a service outage is not sufficient. Eligibility checking does not disclose or grant ordinary Brain content access. Personal Brain ownership cannot be transferred or recovered through these operations.

Transfer or recovery pauses export. The new owner must provide fresh repository credentials and renew destination, full-history, public-disclosure and schedule consent. If a transition receipt is accepted but authorized readback fails, check current ownership before trying again; do not automatically repeat the transition.

## Disable or delete

Use the lifecycle action and its confirmation to enable or disable the Brain. Disabling is not deletion. Delete requires the actual current Brain owner and current owner/lifecycle checks, not a broad administrative role alone.

Read the confirmation carefully and verify the outcome. Deleting a Brain does not erase external GitHub history or copies, and does not revoke independently shared source access. Resolve those separately when planning removal.
