Settings
Settings holds your own settings and the values your organization may set for itself: task tags and schedules, runner quotas, and your organization-wide controls. Only what you can change is shown; the rest is set by Jaah.
Open it from the sidebar: select Settings. Everyone can open it; without permission to view system settings you see only Personal and the Customize pages your role opens.
Type in Search settings to find a value by name. Each of your Personal settings is a result of its own, such as Theme or API keys: selecting it opens its page and lights the setting. A Customize page is found by what you do there, such as new playbook. Each result shows where it lives, for example Personal › Security. Results found only by what a setting does, not by its name, follow under Other matches.

The categories on the left each open their own
list, grouped under headings: Personal (Profile, Preferences, Security, Git; see
Your profile), Organization (General, Tasks,
Features, Integrations, Billing) and Customize (Playbooks, Templates, Agents,
Compliance Packs, Pipelines). The categories you see
depend on your role and plan; a category with nothing you can change doesn't appear. A link straight to a
category opens it, and §ion= with a card's slug opens that card; a link to a category you can't
see says it isn't available here. An address naming no category, such as an old
category name, reads Page not found. Each category's settings sit in titled cards; a Personal or
Customize page sits in a card of its own beside the list. In a narrow window the list is a Category picker beside the
search; on a phone the list is a page of its own, and a category opens over it.

A record with its own page, such as a tag group or a tag, opens beside the list, with the list still showing; the arrows at its top right widen it to the whole window, and the cross closes it. While it is open, Search settings steps aside, unless it holds a search, so the list's own search is the only one.
Reading a value
Each row shows a setting's name and a box or switch holding its value. Hover the name (it is underlined with dots) to read what it does.
Beside the box, Default · and the value the setting has while your organization sets none (not set when that is nothing). Once your organization has its own value, Reset to … takes the place of that line and goes back to it (Clear when that value is nothing). A value equal to the default reads as Default.
A checkbox saves as soon as you tick or clear it, and so does its Reset to …. Every other row waits for Discard and Save at the top of the page; they appear once you change one, and Save counts the rows, for example Save (2). A category and a section with rows waiting show how many, for example 2 unsaved. A refused save marks each row it carried, and the row it names says why, then what is still saved (Still saved: …). When it carried several rows, the message above lists them after Not saved:, or after Nothing saved. Still pending: when the save was refused before anything was written.
General
Shown to an Org Owner or Org Admin. Cards for Organization (name and Slug), Join domains, Sign-in and Background jobs. See Your organization.
Background jobs
Who your organization's background work acts as: the work Jaah starts on its own rather than for a person, such as scanning finished tasks for reverts and fixes. The card shows on every plan.

| Item | Meaning |
|---|---|
| Run jobs as | The member background jobs act as. Type to search your enabled members. Empty, it reads First Owner/Admin: jobs act as your first Org Owner or Org Admin. A project's own Run jobs as, or an automation's Run as, takes its place for that project or automation. |
| Save | Saves the choice; it reads Saved once done. |
Tasks
Defaults
Defaults holds Node picker, shown to an Org Owner or Org Admin. On, anyone who edits a task can pick the node it runs on; off (the default), tasks run on any of the project's nodes.

Board
Board holds Unread glow, shown to an Org Owner or Org Admin. A finished task you have not opened glows on the task list; it stops glowing after this many days (7 by default), opened or not.
Quotas
Quotas holds Concurrent runners: the most runners each subscription model account runs at once, counting runners still starting up. An account's own Max runners overrides it; an API-key account has no limit unless one is set on it. See How model accounts work.

Tags
Tags holds your organization's tag groups, with New group to add one when you may create tags. With none yet, it says No tag groups yet. Selecting a group opens its page, and its row's ⋯ moves it up or down when you may edit tags; see Tag groups and tags. Without the task and tag permissions, the section says Reading the tag vocabulary needs task and tag grants you do not hold. Ask your administrator.
Tag groups and tags
A tag group's page has two tabs; New group opens it as New tag group with Overview only.

| Item | Meaning |
|---|---|
| Status | active or draft, beside the name. A draft group shows Draft — not offered outside this page yet. and is not offered on tasks. |
| Line under the name | One tag per task or Several tags per task, and how many tags the group holds. |
| Activate / Move to draft | Publishes the group, or takes it back to draft. A group with no tags can't be activated. |
| Delete | Deletes the group and every tag in it, after Delete tag group asks you to confirm; its tags come off the tasks carrying them. It can't be undone. |
| Name | The group's heading in Settings › Tags and in the board's Group-by control. |
| Description | What the group is for. Jaah reads it when it tags tasks. |
| Tags per task | One tag (picking a second replaces the first) or Several tags (a task may carry any number). |
| Tags tab | The group's tags, each with its code beside its name; New tag adds one. With none, it reads No tags yet. A group with no tags cannot be activated. Select a tag to open it. ⋯ on a tag's row holds Move up and Move down. |
Cancel and Save (Create for a new group) sit at the foot of Overview; Save turns on once you change something.
A tag's page, Add a tag to … when new, has one tab, Overview; a saved tag has Delete at the top:
| Field | Meaning |
|---|---|
| Name | Shown on tasks carrying the tag. |
| Code | The key a task's tag is stored under. Blank on a new tag makes one from the name: lowercase letters, digits, - and _, at most 32 characters. Once set, it can be changed but not cleared. |
| Description | What earns a task this tag. Jaah reads it when it tags tasks. |
Shortest gap and outcome scan
Shortest gap between schedule runs is shown to an Org Owner or Org Admin. It sets the shortest gap allowed between two firings of one of your schedules.

| Item | Meaning |
|---|---|
| Effective | The minimum in force. |
| Your minimum | Your organization's own minimum, or Not set. The pencil right after it turns it into a box, in seconds; Enter or leaving the box saves, Escape cancels. An empty box clears it. A value under Jaah's is refused, with the reason inside the card, under its title. |
| Set by Jaah | Jaah's minimum. Yours can't be lower. |
Outcome scan interval follows it, shown to an Org Owner or Org Admin when your plan includes Agent performance; without it, the card doesn't appear. It sets how often, in minutes, each project is scanned for reverts and fixes of finished work. A project's own interval, set on the project, overrides it.
| Item | Meaning |
|---|---|
| Effective | The interval in force, for example 60 min. |
| Your interval | Your organization's own interval, or Not set. The pencil right after it turns it into a box, in minutes; Enter or leaving the box saves, Escape cancels. An empty box clears it, so the default applies. A value outside the allowed range is refused, with the reason inside the card, under its title. |
| Default | The interval used while your organization sets none, then the allowed range, for example 60 min · 15–1440. |
Features
Shown to an Org Owner or Org Admin. One card per feature: NodeVault, Intelligent routing, MicroVM, SSO, SCIM, IP allowlist, Audit export, Staging, Your data, Data residency and Providers. A card your plan leaves out doesn't appear, except Intelligent routing, below. See Your organization.
NodeVault
Shown to an Org Owner or Org Admin. NodeVault lets only your organization's nodes open the secrets of credentials marked NodeVault; this card sets it up and lists its keys and nodes. How it works: How NodeVault works.

| State | What the card shows |
|---|---|
| Not in your plan | The card doesn't appear, whether or not NodeVault was set up. Credentials already sealed with NodeVault keep working. |
| In your plan, not set up | Set up, which opens the six setup steps. See Set up NodeVault. |
| Set up | The keys, Rotate key, Audit and the Nodes list, below. |
Once it's set up:
| Item | Meaning |
|---|---|
| Banner | While credentials are moving or an old key is retiring: Credentials are moving to NodeVault. or An old key is being retired., with Offline nodes confirm when they reconnect. |
| Current key | The short hash of the key new NodeVault secrets are sealed with, and the date it became current. |
| Previous keys | Each older key with how many credentials still use it. Retiring shows while nodes are still deleting it. |
| Retire | Deletes a previous key from every node, after Retire key? asks you to confirm. It can't be undone. The line under it says why it's unavailable, for example 1 credential still uses this key. |
| Rotate key | Opens the six rotation steps. See Rotate the NodeVault key. |
| Start over | Shown to the Org Owner when no node holds the current key. Start NodeVault over? asks you to confirm: the key is retired, credentials sealed under it must be entered again, and NodeVault is set up with a new key. |
| Audit | Opens Audit, Activity tab, searching for nodevault. |
The Nodes list shows each node in your organization: its name, Online or Offline, its identity key's Fingerprint (or No identity key yet), and where the key stands on it:
| Status | Meaning |
|---|---|
| Delivered | The node holds the key. |
| Delivering | The key is on its way. |
| Waiting (offline) | The node gets the key when it reconnects. |
| Waiting for a node that holds the key | A node that holds the key must come online to pass it on. |
| Failed — retrying | Delivery failed and is being tried again; the line says why, for example Node didn’t answer in time. |
| Failed | Delivery failed; the line says why. Select Retry. |
| Identity changed | The node lost its identity key. Select Reset identity, then Reset, to enrol it again. |
| Removing | The node is deleting a retired key. |
| Not enrolled | The node hasn't registered an identity key yet. |
| Can't hold keys | Update Jaah on this node. |
| No key | The node doesn't hold this key. |
When the organization has no node, the list says No nodes yet.
Intelligent routing
The highest routing mode your projects may use, and which runners and model tiers routing may pick from.

The card shows on every plan. When your plan doesn't include intelligent routing, it says Intelligent routing isn't included in your plan. and its controls are disabled; Maximum mode can then only be lowered.
Under Mode, Maximum mode; under Policy, the runners and the tier range:
| Item | Meaning |
|---|---|
| Maximum mode | The highest mode a project may choose: Off, Recommend or Auto. It saves as soon as you pick it. Picking a lower mode asks first, in Lower routing maximum: every project set above it drops to it, and raising it later doesn't restore them. |
| Allow every runner | On (the default), routing may pick any runner. Off, it picks only the runners you check in the list that opens below. |
| Lowest tier and Highest tier | The range of model tiers routing may pick from, or No limit. |
| Save | Saves the runners and the tier range. |
Your data
Needs a plan that includes it; without it, the card doesn't appear. See Subscription.
Your data sets how long your organization keeps three kinds of data. Older data is deleted for good each night.
| Field | What it holds |
|---|---|
| Session transcripts | Days to keep agent session transcripts. |
| Activity events | Days to keep activity events. Security events stay at least 365 days. |
| Task artifacts | Days to keep the files tasks produce. |
Each box is a number of days; its hint gives the allowed range, for example 7 to 180 days., and an empty box keeps the default, shown greyed in the box. Save applies the three, Discard puts them back. A value the allowed range no longer admits is shown with Was …; the allowed range changed.
Data residency
Data residency sets the Region your organization's machines, session transcripts, task artifacts and attachments are kept in, with Save and Discard once you change it. What stays in the control-plane region is on the Security legal page, Data location. Two lines under the region say what stays behind and what it does not cover. Once data exists in the region, a note says what is there and the region can no longer change.
Integrations
Shown to an Org Owner or Org Admin. Two lists, each row opening its own page, then the Email card (Email), and the Slack card when your plan includes Slack (Slack):

| Section | What it lists |
|---|---|
| Issue trackers | Your Linear, Jira and Backlog connections, with Add tracker; with none, No tracker connected. See Issue trackers. |
| Webhooks | The URLs Jaah sends your organization's events to, with New webhook; with none, No webhooks yet. Shown only when your plan includes webhooks. See Webhooks. |
Billing
Shown to an Org Owner or Org Admin: your plan, hosted nodes, payments and invoices. See Billing page.
Customize
Playbooks, Templates, Agents and Compliance Packs each open their own page: see Playbooks, Templates, Agents and Compliance packs.
Pipelines
Shown to an Org Owner or Org Admin. The Pipeline rules section sets the checks every project's step into production must pass on each pipeline save, each Off, Warn or Block: Pipeline rules; to roll one out, Set your org's pipeline rules. The Pipeline templates section keeps pipelines many projects share, with a draft you publish after review: Share a pipeline with a template; every field: Pipeline templates.

Related
- Automations: the schedules the cron minimum applies to.
- How NodeVault works: what the NodeVault card sets up.