Atlas credentials
A credential gives Atlas the access it needs to read a private source. Public repositories need no credential; everything else does.
The two kinds
| Kind | What you provide |
|---|---|
| git | An access token (e.g. a GitHub PAT with classic repo scope, or a fine-grained read-only token), plus an optional username (e.g. x-access-token). |
| jira | Your Jira account email, an API token, and the Jira base URL (e.g. https://your-org.atlassian.net). |
Ownership
A credential belongs either to you (personal) or to an org:
- Personal credentials are visible and usable only by you.
- Org credentials are visible to org admins, forming a reusable pool for that org's projects.
The token value is write-only
[!IMPORTANT] Once you save a credential, its token value is never shown again — not in the list, not when you edit it. Others ever only see a credential's name, never its value.
Atlas also never writes a credential's token into a generated page, a log, or a run's events.
Lending a personal token to an org project
You can bind a personal credential to an org project's source without that token entering the org's reusable credential pool. This lets an org project use your private access while keeping the token yours.
- Other org admins can run the project — a run uses the token to clone or fetch — but they cannot see its value or reuse it on other sources.
- On an org project, a bound personal credential is flagged "personal — private to you".
[!WARNING] Anyone who can run a project can use whatever credential it's bound to. If you want a token that only you can use, keep the project personal rather than binding the token to an org project.
Related
- [[Atlas projects & sources]] — where a credential gets bound to a source.
- [[API & personal access tokens]] — tela's own PATs (a different thing from the source credentials here).