FAQ

No. Create a new token and Revoke the old one.

API tokens

I lost the token secret — can Spanline show it again?

insufficient token scope from the CLI

The token lacks permission for that API. Create a new token with the needed area (for example Performance · Read & write for spanline test run) or use the CLI / CI preset.

invalid API token scopes when creating a token

You selected an invalid combination (for example no permissions in Custom mode). Pick at least one access level or switch to a preset.

Token works in the app’s workspace but fails in CI

Check both:

  1. Restrict token to … — token may be pinned to a different workspace than CI expects.
  2. spanline auth workspace use or SPANLINE_WORKSPACE — CLI must target the same workspace.

See Concepts → Workspace restriction.

Last used shows never

Normal for a brand-new token. It updates after the first successful API call with that token.

Should I use one token for everything?

No. Use separate tokens per machine or pipeline so revocation is surgical.

Sign-in & MFA

Password login is disabled

Your organization requires SSO. Sign out and sign in with your work email to continue with organization SSO.

Pages say MFA is required

Open Account → Security and enroll an authenticator before using other workspace features.

I changed my password — do tokens still work?

Yes. API tokens are independent of your password until you revoke them.

Sessions

Revoke vs sign out

Sign out ends your current browser session. Sessions → Revoke can end other devices while you stay signed in here.

I revoked all sessions by accident

Sign in again with email/password or SSO.