Skip to content

Console · Sites

Site Access Tokens

Last updated 18 November 2026

Create, copy and revoke the access tokens that let a script or the CLI reach one site.

An access token lets the Insites CLI, or a script you write, reach a site as you. What you change with it is recorded against your name. Each token expires after 90 days.

An access token is not the same as your personal CLI token, which you find on your My profile page. An access token belongs to one site.

Where to Find It

The Access Token card is the last card on a site's CLI Commands tab. To see it:

  • You need the Developer role or above, because the CLI Commands tab is only shown from that role.
  • The site must run on the Insites private stack. Other sites do not show the card.

Getting Your Token

  1. Navigate to Sites from the main menu.
  2. Find the site on the main page or inside a folder, and select it to open it.
  3. Select the CLI Commands tab.
  4. On the Access Token card, select Get my token. If you already have an active token, the button says Replace my token, and your new token replaces the old one.
  5. Copy your token straight away. It is shown only once, and it is gone when you leave the tab. The card also shows when it expires.

Under the token, the card shows a command that adds this site to the Insites CLI with your token. The Console fills in the address and your token. Copy it and replace the environment name with one of your own. It has this shape:

insites-cli env add <environment-name> --url <proxy-url> --token <your-token>

Run it in your project folder. Update the Insites CLI first with npm install -g @insites/insites-cli --no-fund. Instead of the address, you can give the site UUID, and the CLI works out the address itself:

insites-cli env add <environment-name> --instance-uuid <instance-uuid> --token <your-token>

Add --console-tier staging for a site in the staging Console. After that, use the environment name with any command, for example insites-cli deploy <environment-name>.

Commands that use the token go through the Insites proxy. It checks your role on every request, and records each deploy and change against your name in the site's activity. When it refuses a request, the CLI prints the reason. Assets upload straight to storage, but the rest of one deploy is limited to about 5 MB. For more, deploy in parts with --partial-deploy. See Insites CLI Commands and Options.

What the Token Can Do

What a token can do depends on your role on the site:

  • With the Editor role, the token can read and change records.
  • Anything that changes code, config or assets needs the Developer role. This covers deploys, syncs, page edits, constants, imports and asset uploads.

Viewing and Revoking Tokens

The card lists the tokens you can see. You see your own token. Admins see everyone's tokens on the site. Each row shows:

  • Who holds the token. Your own row says You.
  • The first characters of the token, when it was issued and when it expires.
  • Its status: Active, Expired or Revoked.

To revoke an active token:

  1. Select Revoke on its row.
  2. Select Revoke token in the dialog to confirm.

The token stops working straight away. Anything already done with it stays on record. You can revoke your own token, and Admins can revoke anyone's.

Note: If the card says Couldn’t load, select Try again.