Secrets
A secret is a connection to another service, such as Jira, Slack, GitHub or AWS: the address, the account and the token or key Jaah signs in there with. Tasks use the secrets they are given, and every task on a project can use the secrets attached to it. Jaah never shows a stored value again after you save it.
- Find a service to connect — search the gallery or pick a category, see how a service signs in, and spot the ones you already have.
- Add a secret — store a new connection, for you or for your whole organization.
- Attach a secret to a project — let the tasks on a project use it, and take it away again.
- Replace or delete a secret — put in a new token when the old one changes, or remove the connection.
- Keep a secret to one project — home an organization secret in a project, so its tasks use it as if attached.
- Change a secret's owner — move a secret to another member, to the organization or to System.
- Save a login with its 2FA seed — store a site's login with its two-factor setup key, so agents can sign in where it asks for a code.
- Connect a service through your own app — sign a service in through an OAuth app you registered yourself.
- Find secrets that need attention — list expired, expiring, unused or failing secrets, then fix or remove them.
- Fill in secrets with no value stored — list the secrets that hold no value with Values, then fill each in or delete it.
- Respond to a leaked secret — revoke it at the service, put the new value in Jaah, and check which projects could use it and who changed it.
- Renew an expired secret — select Renew beside an Expired secret and put in a new token.
- Reconnect a secret a service stopped accepting — sign in to the service again on the same secret, so its projects keep it.
- Check a secret's value before you save it — reveal what you typed with Show, and tell that a value is stored without seeing it.
- Test a secret — check that a connection signs in before tasks use it, and read the last result on any secret.
- Connect an API that has no card — store a key for an unlisted service with Generic API key, and set the header and prefix it is sent under.
- Connect an MCP server — add a server from the MCP servers category with its key or a sign-in, then link it to a project.
- Add a custom API or MCP server — define your organization's own service once, then connect to it like any other.
- Change a custom connector's definition — change its address or how it signs in, or delete it.
- Find the projects that use an MCP server — list the projects that link an MCP connection, and unlink it from each.
- Browse secrets by folder — turn on Tree view to see secrets by home and folder, and drag one into another folder.
- Sort the secrets list — order the flat list by Created, Name or Type with ⇅, and keep that order next time.
- Move secrets into a folder — tick several secrets and file them under one folder at once.
- Delete many secrets at once — tick the secrets you no longer need, or all a filter matches, and delete them in one step.
- Find the secrets a member owns — list one member's secrets with the Owner filter, then hand each on or delete it.
- Add a second secret for the same service — connect another account or site of a service, such as a staging Jira, and keep the two apart by name.
- Tell a task which secret to use — copy a secret's runner path and name it in the task.
- Rename a secret or describe it: give a secret a clearer name or a description, and update the runner path tasks use.
- Give agents a Jaah API key — save a key agents use to file and update tasks in Jaah itself.
- Vote for a beta app — ask for one-click Connect on a service marked Beta, and take the vote back.
- How NodeVault works — seal secrets with a key only your organization's nodes hold.
- Set up NodeVault — make the key, back it up, send it to your nodes and move secrets in.
- Rotate the NodeVault key — move to a new key, then retire the old one.
- Abandon a NodeVault key rotation — stop a rotation on its Distribute step and keep the current key.
- Retry secrets a key rotation failed to move — read why a secret didn't move onto the new key, and retry it.
- Move a secret into NodeVault — seal a secret you already have with the NodeVault key, or take it out again.
- Send the NodeVault key to a node again — retry a failed delivery, or enrol a reinstalled node so it can open sealed secrets.
- Connect a service in one click — sign a service in through Jaah's own app, choose its permissions, and retry a sign-in that didn't finish.
Every field and filter is described in the Secrets reference. To hand one field of a secret to a project as a variable, see Add an environment variable. For who owns a secret, how tasks receive it and how it differs from a model account, see How secrets work.