Create a credential

A credential holds the authentication details a toolkit needs to reach an external service — a base URL, a token, or a username and password. You create one, then attach it to any toolkit of the matching type.

1. Open Credentials

   Go to /credentials/all and click Create, or go directly to /credentials/create-credential/<type> for a specific service.

2. Pick a type and fill in the fields

   Select the credential type (GitHub, Jira, Azure DevOps, and so on). Fields vary by type — most ask for a base URL plus a token, or a username and password. Where a field expects a secret, create it first at Create a secret so it’s available in the dropdown.

3. Choose project or private scope

   Project credentials are shared with everyone on the project; private credentials are visible only to you. Pick whichever matches who should be able to use it.

4. Save it

   Give the credential a clear name and save. It’s now available in any toolkit form that takes this credential type.

Attach it to a toolkit

1. Open /toolkits/create/<type> (or edit an existing toolkit of the matching type).
2. Open the credential dropdown and select the credential you created — or create a new one on the fly from the same dropdown, as a project or private credential.
3. Save the toolkit. It now authenticates using this credential.

Note

If your credential doesn’t appear in a toolkit’s dropdown, confirm it saved successfully and that you’re working in the same project — private credentials only appear to the user who created them.

Good practice

• Use descriptive names for both credentials and toolkits.
• Reference secrets from the vault instead of pasting raw values into credential fields — see Create a secret.
• Rotate credentials and secrets periodically, and remove ones you no longer use.