Skip to main content

Keep a secret to one project

An organization secret lives in a home: the organization itself, or one of its projects. A secret homed in a project is filed under it and is usable by that project's tasks, as if attached to it. Names only have to differ inside one home, so each project can keep its own secret under the same name. To tell a task which one to use, copy its path with Copy runner path.

Who can do this: Org Owners and Admins. Other members' secrets are always Personal; to share one with a project, attach it instead.

Home a new secret in a project​

  1. In the sidebar, select Directory, then the Secrets tab.
  2. Select Add secret, then Other secret, or Connect on a service's card.
  3. Pick the Type, check the Name and fill in the type's fields, as in Add a secret.
  4. Open Advanced and pick Organization under Owner. A Home list appears under it, set to your organization's name.
  5. In Home, pick the project. Hover Home for what it does: In a project, its tasks use it as if attached.
  6. Check the line above Type: it now reads your organization, the project, then the name, such as Acme › website › deploy-key.
  7. Select Save.

On a service you connect in one click, the project you pick in Home gets the new secret attached instead.

Move a saved secret to a project​

  1. Select the secret's name in the list to open it.
  2. Open Advanced. On an Organization secret, Home shows where it lives now.
  3. Pick the project, or your organization's name to take it out of the project.
  4. Select Save. Its name in the list now starts with the new home.

A task that asked for the secret by its old path no longer finds it: copy the new one with Copy runner path in the secret's row and update the task. See Tell a task which secret to use.