Secrets
A secret is a connection to another service, such as Jira, Slack, GitHub or AWS. It holds the address, the account and the token or key Jaah uses to sign in there. Tasks can use the secrets they are given, and so can the projects you attach a secret to.
Open it from the sidebar: select Directory, then the Secrets tab.
Everyone can open it. The list shows only the secrets you can see: the ones you added, and the ones shared with you. Everyone can select Add secret and change or delete the secrets they added. Changing or deleting other people's secrets needs permission: without it, Edit or Delete doesn't appear on that row. An Org Owner or Admin can also move any secret they can see to another owner; see Advanced.
The list

A header row names each column. From left to right:
| Column | Meaning |
|---|---|
| Round mark | Filled: at least one secret, such as a token or key, is stored. Hollow: none is stored yet. Hover it to see how many. |
| Name | The secret's home in grey, for example Sales › website ›, then its name. Hover the row to show Copy runner path beside it. A NodeVault secret has a ◈ mark and its key's short hash after the name; hover the mark for NodeVault · key and the hash. An expired secret shows a ⏱ mark and Expired after the name, in red, and on a secret you can change a red ↻ Renew that opens it to enter a new value or reconnect; one that expires within 7 days shows Expires in 3d, in amber. |
| Description | What the secret is for, or — when none is set. Shown only in a wide window, and hidden while a secret is open beside the list. |
| Used | How long ago a task last fetched it, for example Used 3d, or Never used. In a narrower window this column is headed Health, and an expired or soon-expiring secret shows Expired or Expires in 3d there instead; the name then keeps only its ⏱ mark. |
| Owner | Organization or System for a shared secret; for a personal one, the member it belongs to. |
| Type | The service it connects to, for example AWS or GitHub. |
| Checkbox | Ticks the row. The header's checkbox ticks every row shown. See Act on many at once. |
| ⋯ | The row menu. The header's ⇅ sets the order. |
Used is hidden while a secret is open beside the list; hover a name to read it.
Select a name to open that secret. See A secret's details. With no secrets at all, the list says No secrets yet.
Order
The list starts newest first. Select Name or Type in the header row to order by it, A to Z; select it again to reverse it, Z to A. ⇅ above the ⋯ column offers Created, Name and Type; picking the active one again reverses it, and its arrow, ↑ or ↓, shows which way. Created reads newest first, then oldest first.
Pages
The list shows 25 secrets to start. Below it a count says how many are shown, for example 25 of 137. When there are more, Load more adds the next 25. Past 10,000 matches the count stops there and reads 10,000+. Changing a filter or the order goes back to the first 25, and so does reloading the page.
The row menu

- Copy runner path copies the path a task asks for this secret by:
org/<name>,projects/<project>/<name>orme/<name>. A row with no runner path shows Copy name instead, which copies its full name: a System secret, which tasks never use, or another member's personal secret. - The next line names the owner. In a narrow window, the description appears here too.
- On a NodeVault secret, a line names its key: NodeVault · key and the short hash.
- Renew opens an expired secret, as the ↻ Renew beside its name does. It appears only on an expired secret you can change.
- Edit opens the secret. It appears only on a secret you can change.
- Delete removes it. See Delete a secret.
Filter the list
Use the controls above the list. Each one narrows the list at once, and the page remembers your choices the next time you open it in the same browser.
| Control | What it does |
|---|---|
| Search | Shows secrets whose name or description contains the text. Its placeholder reads Name or description. |
| Type | Shows one type of secret. Any shows every type. |
| Owner | Type a name or email, then pick one or more people to show their secrets. Remove a person with their ×. Empty, it reads Any and shows everyone's. It appears only when the list has more than one owner. |
| Values | Stored or Not stored. Any shows both. |
| Health | Expired, Expiring (7 days) or Never used. Any shows all. |
| Only mine | Shows only the secrets you created. Select it again to turn it off. |
| Tree view button | Switches between the flat list and the tree. See Tree view. |
When nothing matches, the page says Nothing matches these filters and lists what is active. Select Clear filters to show everything again.
Tree view
Select the Tree view button at the end of the filters to group secrets into folders. The top level
lists each home: the organization's shared secrets, system, each project and each person with secrets
of their own. Inside a home, a name's parts between
slashes become folders: team/prod/jira sits in the folder prod, inside team. The number beside a
folder is how many secrets it holds under the current filters; past 1,000 it shows 1,000+.
- Select ▶ beside a folder or home to open it. Its contents load when you open it.
- When a folder holds more than one page, select Load more at its end.
- To move a secret to another folder in its home, drag it onto that folder, or onto the home to take it out of its folders. Its name changes to match. Requires permission to edit the secret.
The folders you open stay open the next time you visit; a folder that no longer exists is closed.
Select Tree view again to go back to the flat list.
Act on many at once
In the flat list, each row has a checkbox at its right end. The checkbox in the header row ticks every row shown. Once they are all ticked, a line offers Select all N matching: every secret the current filters show, not just the ones loaded; Clear selection undoes it. Changing a filter or the order clears the selection.
The bar above the list says how many are selected and offers:
| Action | What it does |
|---|---|
| Delete | Deletes them all. You type the count to confirm. This cannot be undone. |
| Move to folder | Files each one under the Folder you type, keeping its own last name part: a/b/jira moved to team becomes team/jira. Leave the folder empty for the top level. |
Each action runs on the whole selection or not at all. It is refused, and nothing changes, when:
- you may not delete or change one of them (the message names which);
- the selection changed since you confirmed it (The matching set changed — review and retry);
- a moved name is already taken in its home (the message names it);
- a secret backs Jaah-managed NodeLink storage (Delete).
One action takes at most 10,000 secrets. Over that, the actions are unavailable: narrow the filters first.
Add a secret
Select Add secret. The integrations gallery (Secrets › New secret) opens beside the list, one section per category under its name, categories A to Z. Each card is a service Jaah connects to. While you search or pick a Category, the cards form one list. OAuth means you sign in at the service, Key that you paste a key, token or password, MCP that agents reach it through its MCP server. Cards in the MCP servers category don't repeat MCP: the category already says it.


From top to bottom:
| Control | What it does |
|---|---|
| Other secret | At the top right. For a type with no card: it opens the form below on Generic Login/Pwd; pick any other type in Type. |
| Search integrations | Finds a service by its name, category or summary. |
| Category | Shows one category. All shows every category. |
| Clear | Shown while a search or a category is set. Drops both. When nothing matches, the gallery says No integrations match, with its own Clear. |
Each card, from left to right:
| Part | Meaning |
|---|---|
| Logo and name | The service. |
| Summary | One line on what it connects. |
| Beta | Not ready for one-click Connect yet. |
| Category | Shown only while you search with Category on All. |
| OAuth, Key, MCP | How it signs in. |
| Connect | Opens that service's screen. See Connect a service. Reads Add another once you have a secret for it. On a custom connector your organization defined, it opens the connector's Connections tab. |
| Add custom | On Custom connector and Custom MCP server, for org admins only. Defines a new REST API or MCP server. See Custom connectors. |
| Vote | On a Beta card, in place of Connect. Asks for it: one vote per person, thanked with Thanks for voting!. It then reads Voted; select it again to withdraw. Where the service also takes an API key or your own OAuth app, Connect stays beside it. |
| Docs | The service's own page, in a new tab: what agents can do with it and where to find each value. |
| State | Once you have a secret for it: Connected, Test failed, Needs reconnect or Untested, with a count when you have several (Connected · 2). |
Generic API key and Generic login, in the Custom category, store a key or a login for a service with no card of its own.

The form asks only for what the secret needs. A label with a dotted underline, such as Name, explains itself on hover. From top to bottom:
| Field | Meaning |
|---|---|
| Home | The line above Type: where the secret lives, for example your own secrets or the organization's, ended by the Name as you type it, such as Sales › website › Jira. It follows Owner and Home in Advanced, and can't be typed. |
| Type | The service it connects to; it decides which fields follow. Type in the box to search the list; No matching secret type means nothing matches. Chosen first. Not shown on a service's own screen, which already names it. |
| Name | The secret's name inside its home, for example aws or jira/prod. Slashes make folders. Names are saved in lowercase, and two secrets in one home can't share a name. Starts as the type's short name, for example jira. Left as it starts and already taken, Save numbers it: jira-2, jira-3. Required for Save. |
| NodeVault | Shown only where NodeVault can be used for this type, or on a secret already in it. Ticked, only your organization's nodes can open the secret's values; hover it for the key that seals them. See How NodeVault works. |
| The type's fields | They change with the type: Jira asks for a Base URL, an Account email and an API token; AWS for an Access key ID and a Secret access key. A secret field shows Show once you type in it; it reveals what you typed, and Hide masks it again. Generic Login/Pwd and Generic API Key take any URL: one that doesn't read as protocol://host:port turns yellow, and hovering its ⚠ says so. A Jaah secret's URL starts as the console you are using; its Key is New, which makes a Jaah API key on Save (every permission you hold, no expiry, named after the secret), or Existing, which picks one of your own keys in Existing key (Choose a key) and takes its pasted API key. New is offered only on a new secret for this console; see Give agents a Jaah API key. |
| Advanced | Folded. Holds the owner, the connection's permissions, Description and the type's optional fields. URL (optional) is the exception where a type needs one and has no standard value, such as Generic API Key: it shows with the other fields. |

Select Save to create the secret, or Cancel to close the form without saving. Leaving with changes not saved asks first, under Unsaved changes: Save saves and leaves, Discard leaves without saving, and Cancel stays on the form.
Advanced

| Field | Meaning |
|---|---|
| Owner | Who, and which tasks, can use it. Personal (the default): one member's; their tasks can use it, and so can the projects they attach it to. Organization: shared; Org Owners and Admins can use it, and so can their tasks and tasks on the projects it's attached to. System: for Jaah itself, for example cloud nodes and Git apps; Org Owners and Admins see it, tasks never do. Only a Jaah operator is offered System; a secret that is already System keeps it as a choice. Shown to Org Owners and Admins, on a new secret and on a saved one, where Save moves it to the owner picked, even on a secret they can't otherwise change. |
| Owned by | With Personal: the member the secret belongs to. Empty, it reads You and keeps it yours; search by name or email to make it another member's. Shown only when you can read the People list. |
| Home | With Organization: the organization or one of its projects. A secret homed in a project is usable by that project's tasks, as if attached to it. |
| Permissions | For a type with Connect: what the service is asked to allow. Each optional permission has a box, all ticked on a new secret and the granted ones once connected; hover the mark beside Permissions for the ones always included. |
| Description | What the secret is for. Shown in the list, and readable by every task allowed to use the secret, so never put a secret here: a ⚠ marks text that looks like one. |
| Optional fields | The type's fields that can stay empty, for example Jira's Project key, or Generic Login/Pwd's 2FA seed: the code-generating seed shown when the account set up two-factor sign-in, kept secret like the password. |

Connect

Some types, such as Figma, sign in to the service instead of asking for a token. They show a Connect button named for the service, for example Connect Figma, and none of the fields it fills. A type that also takes a pasted token shows its fields with the button below them. Jira, for example, shows only its fields until Jaah has a sign-in app for it.
Select it to save the secret and go to the service to allow access. Name starts as the type's short
name, for example figma. Back in Jaah, the secret opens and says Connected. when it worked.
A type built on your own OAuth client also shows Redirect URI with Copy redirect URI: register that exact address with the client before you connect. When Connect can't start, it is greyed and a line under it says why; hovering it says the same. Where Jaah has no sign-in app for that service yet, the button isn't shown: paste a token in the fields instead, where the type takes one.
Connect a service
A service's screen (Secrets › New secret › the service) names it, with its logo, a one-line summary and Docs. It has no Type: the service sets it. Under Connect with it offers each way the service signs in, in the service's own order. A service with one way in shows no Connect with. The fields below change with the choice.
| Choice | What happens |
|---|---|
| Connect service | Hover text: Sign in at the vendor through Jaah's app. Select Connect service and allow access at the service. Nothing is saved until you do; back in Jaah the secret opens, already tested. Not offered on a Beta service, which has no Jaah sign-in app yet; where nothing else signs it in, the screen shows no Connect with and its Connect service button stays greyed. |
| Use an API key instead | Hover text: Paste the vendor's credentials into the fields below. It drops instead when it is the first choice, as in Use an API key. It names what the service takes, after the fields it asks for: Jira reads Use account email and API token (with instead after a Connect Jira choice); others read, for example, Use a service account key. The service's own fields, each explaining on hover where the service shows it, saved with Save. |
| Use your own OAuth app | Hover text: Sign in through an OAuth app you registered yourself. Your own app's Client ID and Client secret, plus the Redirect URI to register in it. Then the same Connect as above. |

A service that lives at your own address, such as Backlog, asks for it before either sign-in (Backlog's Space URL); Connect stays off until it is filled. While Connect is off, a line beside it says what to do first, such as Enter the space URL first. or Enter the client ID and secret first., or Not available yet. Vote for it in the gallery. on a Beta service. Backlog is Beta, so it signs in with an API key or your own OAuth app.
With Connect service or Use your own OAuth app chosen, the form has no Save: the Connect button saves the secret once the service allows access. For an Org Owner or Admin, Owner in Advanced then offers only Personal and Organization, with no Owned by: a personal secret made this way is always yours. A few services, such as Slack, decide the owner themselves, and Owner isn't shown. Permissions in Advanced lists what Connect asks the service for. With Use an API key instead, Owner works as on any secret, and Save saves it.
When the sign-in at the service doesn't finish, you come back to the same screen with nothing saved and a red line saying why, such as The authorization was not completed, so nothing was stored. or The connect attempt timed out. Connect again. Select Connect service to try again.

When another form sends you here to add a secret it needs (Add new… in a secret picker, or an Add secret link), Save and Cancel take you back to that form. From a picker, the new secret is already picked after Save.
A secret's details
Select a secret's name, or Edit in its row menu. It opens in a pane beside the list, with the tabs Details and Access, and MCP for an MCP connection.
Beside its name, the secret's state: Connected (its last test passed), Test failed, Untested, or Needs reconnect when the service refused it for good. Under it, the last test's message and when it ran; a secret that needs reconnecting offers Reconnect where Jaah can sign in to that service for it.
If you open a link to a secret that belongs to another of your organizations, the page says This belongs to that organization and offers Switch to it. Nothing switches until you select it, and the organization may ask you to sign in again. A secret you can't reach in any of your organizations shows Secret not found.
Details

The same fields as when you added it. Secrets are never shown again. A stored one shows dots (●●●●●●●●●●●), which clear when you select the field. Leave it empty to keep the stored value; type a new value only to replace it. Show appears once you type; a field you empty masks again. See Check a secret's value before you save it.
A date Jaah writes itself, such as when a token expires, shows as a date you can't type over; Clear empties it.
Turning NodeVault on or off re-seals every value, so each secret field asks you to re-enter it before Save (Re-enter to turn NodeVault on.). Changing the address a secret is sent to, such as Jira's Base URL, does the same: each stored value reads Re-enter: the Base URL changed. and can't be kept.
A secret whose type the console no longer supports shows a warning instead of its fields: delete it, or create a secret of a supported type.
Under Advanced, an Org Owner or Admin sees Owner and Owned by with the secret's current owner; picking another one and selecting Save moves the secret to it.

Change what you need, then select Save. Select Cancel to discard your changes. When the pane closes, the list beside it updates to show your change.
If you can't change the secret, the tab says Read-only and who can: a personal secret's owner, or an org admin for an org or system one. Every field is locked, Save is gone and Cancel reads Back, except for an Org Owner or Admin, who keeps Owner and Save to move it.
Access
Who owns the secret and which projects can use it.

| Item | Meaning |
|---|---|
| Owner | The person who owns it, or Organization or System. Select a person's name to open them on the People page. |
| Projects | The projects it's attached to, or No projects. Tasks on those projects can use it. Select a name to open that project. |
- To attach it to a project, pick the Project, then select Attach.
- To take it off a project, select Detach on that project's row and confirm. Tasks on that project stop receiving the secret.
A System secret can't be attached to a project. The tab says so instead of showing the picker.
MCP
The projects that link this MCP connection, so their agent sessions reach its server. Select a project to open its Settings tab at the MCP section, where links are made and removed. With none, the tab says No project links it yet.
See Projects for a project's own settings.
Delete a secret
Select ⋯ on a row, then Delete.

Deleting removes the secret and every value stored with it. It can't be undone. Select Delete to confirm, or Cancel to keep it.
When it is the last GitHub secret you can see, the dialog warns first: Deleting the only set of GitHub credentials will prevent Jaah from implementing any new functionality. Deleting many at once warns the same way.
Custom connectors
A custom connector is your organization's own REST API or MCP server, defined once so members can connect to it like any other service. Find them under Add secret, in the Custom category: each connector is its own card.
Everyone can open a connector and connect. Defining, changing and deleting a connector requires the org admin role.
New
In the Custom category, org admins select Add custom on Custom connector (a REST API) or Custom MCP server. Each opens the Definition form below; Create saves it and opens its Connections tab.
Definition

The fields follow the kind and the Auth choice. Members see the same facts, read-only.
| Field | Meaning |
|---|---|
| Name | The connector's name. Required. |
| Description | What it is for. Shown in the list. |
| Base URL / Server URL | The address of the REST API or the MCP server. Required. An MCP server, or a REST API with OAuth2, needs a public https:// address. Otherwise any URL saves: an odd one turns yellow, and Test needs http:// or https://. |
| Auth | How a connection signs in. REST API: Bearer token, Header key, Basic or OAuth2. MCP server: None, Bearer token or OAuth2. |
| Header | With Header key: the header the key is sent in, for example X-API-Key. Required. |
| Prefix | REST API, with Bearer token or Header key: sent before the key; blank for none. Bearer by default for a bearer token. |
| Authorize URL, Token URL | REST API, with OAuth2: the service's sign-in addresses. Required. |
| Scope | With OAuth2: what to ask for, space-separated. An MCP server's sign-in addresses are found from its server URL. |
| Test path | REST API: where Test sends a GET, for example /v1/me. |
| Transport | MCP server: Streamable HTTP or SSE. |

Create saves a new connector and stays greyed until the required fields are filled. Save saves an existing one; Cancel goes back to the Custom category. ⋯ beside the name offers Delete, refused while connections use it.
Connections
The connector's connections you can see, each with its Owner (Org or Personal), its Health (OK, Test failed, Untested, Needs reconnect, or Not testable for a NodeVault connection, which Jaah's servers can't open) and, on a connection you can edit that isn't in NodeVault, Test, whose result shows above the list. Select a name to open that secret (A secret's details). With none, the tab says No connections yet.
Connect below the list adds a connection:
| Field | Meaning |
|---|---|
| Name | The new secret's name. Required. |
| Owner | Personal or Organization. Shown only when you may create organization secrets. |
| The connector's inputs | What its Auth takes. REST API: API key (Bearer token, Header key), Login and Password (Basic), or Client ID and Client secret (OAuth2). MCP server: Token (Bearer token), optional Client ID and Client secret (OAuth2), or nothing (None). |
Connect saves the connection. With OAuth2, sign-in continues on the secret's page: once saved, the tab offers Connect it.