Skip to main content
Only an Owner, Admin, Network admin or IT admin can create an OAuth client. A Network admin cannot grant the Users or Devices Core write scopes, so an Owner, Admin or IT admin must create the client if you need user or device changes.

Create the OAuth client

An OAuth client belongs to your tailnet, not to a person. It keeps working after its creator leaves the tailnet, and the access tokens it creates last one hour and renew automatically.

1

Sign in to Tailscale

Sign in to your Tailscale admin console.

Trust credentials page with the Credential button highlighted
2

Choose OAuth

On the New credential page, select OAuth. In Description, enter a name you will recognize, such as StackOne Integration, then select Continue.

New credential page with OAuth selected, a description entered and the Continue button highlighted

Choose the scopes

The Scopes step decides what the connection can read and change.

1

Select All - Read

Open the Scopes list and select All - Read.

  • The connection test lists users, groups and pending invitations. Tailscale names no scope for pending invitations, so the client needs read access to the whole tailnet.
  • All - Read cannot change anything. It reads users, devices, DNS, the policy file, logs, webhooks, settings and every access token in the tailnet, plus any read API Tailscale adds later.
Scopes list open with the All - Read option highlighted
2

Add write scopes you need

With All - Read selected, every Read box is ticked and locked, and each Write box stays available. Tick Write only for the actions you use.

  • Users under General, to suspend, restore, approve, delete or change the role of users.
  • Core under Devices, to authorize, tag or remove devices.
  • DNS and Policy File under General, to change DNS or replace the policy file.
  • Webhooks under Keys, so StackOne can create the webhook for event subscriptions.
  • Leave every Write box clear to keep the connection read-only.
Scopes step with All - Read selected and the Read boxes ticked
3

Generate the credential

Select Generate credential.

Bottom of the Scopes step with the Generate credential button highlighted

Copy the client ID and secret

The Credential created dialog shows both values StackOne needs.

1

Copy both values

Copy the Client ID and the Client secret with the copy buttons, store them securely for use later, then select Done.

  • The client secret is only displayed once and cannot be retrieved later. If you lose it, create a new credential.
  • The client secret starts with tskey-client- and is case-sensitive.
  • Paste the Client ID into the OAuth Client ID field and the Client secret into the OAuth Client Secret field in StackOne Hub.
Credential created dialog with the Client ID and Client secret copy buttons highlighted and the secret masked

Revoke the OAuth client

Tailscale OAuth clients do not expire. The client works until you revoke it.

1

Open the credential menu

On the Trust credentials page, open the menu at the end of the credential’s row and select Revoke….

Credential row menu open with Revoke highlighted
2

Confirm the revocation

Select Revoke credential.

  • Revoking the credential also revokes any active access tokens created with it, and the connection stops working until you paste a new client ID and secret into StackOne Hub.
Revoke credential dialog with the Revoke credential button highlighted
1

Connect

  • Click Connect.
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup.
2

Use Actions

Connect an AI platform to the linked account’s actions. See AI Platforms.Other ways to call actions are listed in Protocols & SDKs.

Next Steps

Webhooks setup

Configure receiving Events for Tailscale into StackOne.