Settings

Settings answers one question: how are this tenant, your organization and your own account set up? Its line under the title reads "This tenant, your organization, and you."

Settings has a side list instead of tabs, in three groups. It shows only the pages your role can change, and opens on the first of them. Someone who may change nothing sees "There are no settings you can change in this organization", with a link to their keys on Connect › Keys.

Who sees whatCopy Anchor Link

Tenant settings works on the tenant chosen in the switcher at the top of the sidebar, and Organization reads its usage figures from that tenant.

This tenantCopy Anchor Link

Tenant settingsCopy Anchor Link

The settings of the tenant you are in, headed Settings for the tenant's name, in up to three tabs. Each tab is shown only if your role may change it:

• Models: the model that powers enrichment, entity extraction, recall, contradiction detection and chunking, a fallback model, and the embedding model. Leave them on Caura Provided to use the platform default, or bring your own provider key.
• Features: switches for what Caura does with this tenant's memories, such as LLM Enrichment, Entity Extraction, Recall Synthesis, Semantic Dedup, Auto-merge near-duplicates and Lifecycle Automation. Skill Factory and the Interviewer are switched on here too.
• Content Policy: what the tenant accepts (personal data, payment data and secrets; business versus personal content) and the recent governance actions. It needs the permission to manage governance. See Content policy setup.

Models and Features save together; Content Policy saves on its own.

OrganizationCopy Anchor Link

OrganizationCopy Anchor Link

Your organization's name and domain. Where it is switched on, a card lets you prove you own your email domain.

Where billing is on (caura.ai), a Plan and usage section shows your current plan with Upgrade plan (and Cancel subscription on a paid plan), and usage this period. The Plan and billing entry in the account menu opens this section. A self-hosted install has no plan: the section is called Usage and shows only usage against the license, and the menu entry is not shown. This page was called Plan and billing until October 2026; typing that in the ⌘K palette still finds it.

At the bottom, Danger Zone deletes the organization, after you type its slug to confirm. It cannot be undone. See Delete your organization.

MembersCopy Anchor Link

The people in your organization. Invite a member, see everyone with their role, and see pending invites. People who can also create and manage tenants see and set each member's tenant access here. Where the newer organization features are switched on, you can also invite many people at once (not on the free plan) and approve requests to join from people whose verified email is on a domain your organization owns.

TenantsCopy Anchor Link

Your organization's tenants: every shared tenant and your own personal one, with each one's members, when it was created and its tenant_id.

• New tenant creates a shared tenant, if your plan allows another. If it does not, the page says so.
• Members opens a tenant's members: add people from your organization with a role (Owner, Admin, Member or Reader), change a role or remove someone. No one else can be added to a personal tenant.
• Rename changes the name; the tenant_id never changes.
• Delete suspends a shared tenant after you type its name: its members lose access and its keys stop working, but its memories are kept. A personal tenant can't be deleted, nor can the organization's last tenant. To delete the tenant you are in, switch to another first.

See Tenants.

RolesCopy Anchor Link

Custom roles for your organization: create a role, choose its permissions and edit or delete it. Built-in roles can't be edited or deleted.

Custom roles are switched on per organization. Where they are off, the page says "Custom roles aren't switched on for this organization", with Ask us to turn it on.

Onboarding defaultsCopy Anchor Link

What a new member gets when they join, whichever way they arrive. Existing members are unaffected.

• Default role: used only where nothing else names a role.
• Tenant access: the shared tenants a new member is added to, and the role they get in each.
• Where they land: the tenant a new member opens on, one of the granted ones; otherwise they land in their own.

Setting tenant access needs the permission to create and manage tenants, and the default role needs the permission to manage members; without them those fields can't be changed.

Onboarding defaults are switched on per organization. Where they are off, the page says "Onboarding defaults aren't switched on for this organization", with Ask us to turn it on.

Agent monitoringCopy Anchor Link

One switch: Record where agents reach. When it is on, your organization's Caura brokers record the programs your agents run, the hosts and external services (MCP servers) they contact, and whether they touch credential or system files. They never send the commands themselves, file paths, the rest of a web address or any content. The brokers pick up a change within about a minute. What they record shows on Home and in the audit trail, to people who can view the organization's audit log. See Where agents reach.

The page is listed only where Broker Fleet is switched on for your organization.

YouCopy Anchor Link

Profile and passwordCopy Anchor Link

Who you are signed in as (name, email, organization and role), and a form to change your password. If you signed in with GitHub or Google and never set a password, use Forgot password on the sign-in page to create one.