Join our Newsletter — 33% off our NHI Course
Home› Guides› Work SaaS API tokens: Leak Response for Notion,…
Guide Secrets Management

Work SaaS API tokens: Leak Response for Notion, Asana, Airtable, Linear and Figma

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 28 October 2026 12 min read
On this page

Tokens for collaboration tools such as Notion, Asana, Airtable, Linear and Figma usually act as the person who created them, so a leaked token exposes everything that person can see: roadmaps, designs, customer lists, incident notes and sometimes other credentials pasted into pages. These tools hold some of an organisation's most sensitive working data, yet their tokens are often created by individuals for quick scripts and automations, stored in notebooks or CI variables and forgotten. This page sets out, per platform, what each token type can reach, how to revoke and replace it, what GitHub secret scanning detects, and how to shrink the blast radius next time. It is for SaaS administrators, security operations and engineers who build integrations. For Slack, GitHub and Salesforce tokens see the SaaS API Token Security Guide; for Jira and Confluence see the Atlassian API Tokens Security Guide.

Key takeaways

  • Personal tokens inherit the person: Notion and Airtable personal access tokens act as their creator, Asana PATs act on your behalf, so a leak is as wide as that user's access.
  • Revocation is immediate but owner-driven: most of these platforms let only the token's creator revoke a personal token from their own settings, so the response depends on reaching that person or an administrator with equivalent power.
  • OAuth gives you better levers: Linear OAuth access tokens last 24 hours and can be revoked through /oauth/revoke; Notion public connections use refreshable OAuth tokens, unlike static internal tokens.
  • Provider notification is partial: GitHub's partner programme notifies Notion (API tokens), Linear and Figma about public leaks, but not Asana or Airtable, and Asana legacy-format tokens have no push protection.
  • Assume data was read: the main harm from these tokens is data access, so leak response is also a data exposure assessment.

How identity and access work in work SaaS platforms

PlatformToken types (vendor docs)What a token reachesLifetime
NotionInternal connection token; public connection OAuth access and refresh tokens; personal access tokensInternal connections see only pages shared with them ("Add connections"); PATs act as the creator with that user's permissionsInternal tokens static; OAuth refresh returns a new access and refresh token
AsanaPersonal access tokens; OAuth; service account tokens (Enterprise tiers)Acts on behalf of the user"Persistent by default"
AirtablePersonal access tokens; OAuth; service account PATs (Enterprise); legacy API keysOnly the scopes and bases or workspaces granted, acting as the creating userNo expiry described; legacy API keys stopped working on 1 February 2024
LinearPersonal API keys; OAuth access and refresh tokens; client credentials tokensPersonal key as the user; OAuth limited by scopes such as read, write, issues:create, adminOAuth access 24 hours; client credentials 30 days
FigmaPersonal access tokens with scopes; OAuth apps; SCIM API tokenScoped endpoints (for example file_content:read) on behalf of the userNot stated for PATs in the pages checked

Airtable's documentation tells developers to treat tokens as opaque, variable-length strings, and Asana says token formats may change without notice. Detection should therefore rely on maintained secret scanning patterns rather than home-made regular expressions.

Admin roles and privileged access

  • Notion: only workspace owners can create internal connections, and tokens are found in the connection's Configuration tab in the Developer portal. Keep the list of owners short, because each owner can create a token with access to whatever pages get shared with it.
  • Asana: Enterprise+ tiers provide admin controls in the Manage apps panel that affect how PATs are handled. Use them to restrict or review PAT use rather than relying on individuals.
  • Airtable: Enterprise admins can create PATs for service accounts from the Admin Panel, which keeps automation off personal accounts.
  • Linear: every admin in the workspace that owns an OAuth app gets access to it, so Linear recommends a dedicated workspace for OAuth apps. Client secrets and webhook signing secrets are rotated separately under Settings, API, and the admin scope should be requested only when truly necessary.
  • Figma: the SCIM API token provisions and deprovisions users, so treat it as an identity administration credential, not an integration convenience.

Integrations, API tokens and service accounts

  • Prefer OAuth or service accounts over personal tokens: Asana advises OAuth when an app acts for other users; Airtable and Asana offer service account tokens on enterprise plans; Linear supports client credentials tokens with actor=app, so changes are credited to the application rather than a person.
  • Grant the least data: Airtable PATs can be limited to specific scopes and bases; Notion internal connections only see pages explicitly shared with them; Figma and Linear scopes limit endpoints. Use them, and review sharing on Notion pages connected to integrations.
  • Short-lived where possible: Linear OAuth access tokens expire after 24 hours (expires_in 86399) and refresh tokens rotate on each use; Linear asks client credentials callers to request a new token at the start of each run.
  • Store tokens properly: Asana recommends a secrets manager, loading secrets into memory at runtime and keeping them out of logs and repositories.
  • Retire project tokens: tokens made for migrations and one-off syncs outlive the project. In the Schneider Electric Jira breach, credentials from an infostealer-infected laptop, including migration credentials, were linked to the intrusion and the attacker claimed a bulk pull of about 400,000 user records over a REST API.

Logging and detection

Secret (GitHub name)Partner alertPush protectionValidity check
Notion API TokenYesYesYes
Notion Integration TokenNoYesYes
Notion OAuth Client SecretNoYesNo
Asana Personal Access TokenNoYesYes
Asana Legacy Format Personal Access TokenNoNoYes
Airtable Personal Access TokenNoYesYes
Airtable API Key (legacy)NoYesNo
Linear API Key and OAuth Access TokenYesYesNo
Figma Personal Access TokenYesYesYes
Figma SCIM API TokenYesYesNo

"Partner alert" means GitHub tells the provider when the secret appears in a public repository. For Asana, Airtable and Notion integration tokens your own scanning is the only automated public-leak signal, and old-format Asana tokens will not be blocked at push time. A found Airtable legacy API key is low risk now that those keys can no longer access the API, but its presence suggests other old secrets nearby.

  • Usage signals: bulk reads or exports of bases, projects, pages or files; API activity from new IP ranges or outside working hours; new integrations, connections or OAuth apps; new webhooks pointing to unknown URLs.
  • Audit logs: enterprise tiers of these tools generally offer audit logs (Figma's Activity Logs API requires an OAuth app). Export them to your SIEM so API activity can be tied to a token and a person.
  • Content scanning: people paste credentials into Notion pages, Asana tasks and Linear issues. A token for one of these tools can therefore expose other secrets, so include the workspace content in secret scanning where your tooling supports it.
MetricTarget
Integrations running on personal tokens rather than OAuth or service accountsFalling to 0
Tokens with a recorded owner and purpose100%
Tokens unused for 90 days still active0
Time from leak alert to revocationUnder 4 hours
Leavers whose personal tokens were revoked on exit100%

Leak response, step by step

  1. Identify the token and its owner: platform, token type, creating user or service account, and what it was granted (Airtable bases and scopes, Notion pages shared with the connection, Linear scopes).
  2. Revoke or regenerate:
    • Notion: for an internal connection, a workspace owner replaces the token from the connection's Configuration tab, or removes the connection from shared pages if replacement is not immediately possible (the authorisation page checked does not describe rotation steps). For OAuth, revoke the connection and re-authorise.
    • Asana: deauthorise the PAT in the developer console (app.asana.com/0/my-apps); enterprise admins can use Manage apps controls.
    • Airtable: delete the token or regenerate it at /create/tokens. Regenerating immediately rejects the old token and keeps the name and permissions, which is the fastest safe path for automations.
    • Linear: revoke OAuth tokens with POST /oauth/revoke; delete personal API keys in Security and access settings. Rotating the client secret invalidates client credentials tokens but not user access or refresh tokens, so revoke those separately.
    • Figma: Settings, Security, Personal access tokens, select the token, Revoke access. Rotate the SCIM token if it leaked and check for unexpected user provisioning.
  3. If the owner is unreachable or has left: suspend the user account through your IdP and SaaS admin console as a containment step, but confirm the token is actually rejected afterwards, because token behaviour on user suspension is not documented for every platform here.
  4. Assess data exposure: list what the token could read and, from audit logs where available, what it did read during the exposure window. Look for secrets stored in pages, tasks, records or issues and rotate those too.
  5. Restore integrations on a narrower credential: an OAuth app or service account with limited scopes and bases.
  6. Close the cause and record the incident using the Leaked Credential Response Playbook.

Revoke now or replace first? Use the token's reach to decide.

SituationDecisionReason
Token found in a public repository, package or paste siteRevoke immediately, accept the outagePublic leaks are harvested by automated scanners
Token with admin scope, SCIM rights or access to all bases or workspacesRevoke immediatelyCan change users, integrations or data at scale
Read-only, narrowly scoped token found in an internal log or private repositoryReplace first (Airtable regenerate keeps name and permissions), then revoke within hoursLower exposure; avoids breaking business workflows
Token belonging to someone who has leftRevoke and rebuild the integration on a service accountNobody can vouch for its use

Whatever the decision, record the exposure window from the earliest time the token could have been seen to the time it was rejected; that window drives the data exposure review.

Hardening baseline

ControlPlatforms (vendor docs)Framework anchor
Service accounts or OAuth for automationAirtable and Asana service accounts; Linear client credentials with actor=app; Notion public connectionsNIST SP 800-53 AC-2 Account Management; CSF PR.AA-01
Scope and data minimisationAirtable scopes and bases; Notion page sharing; Linear and Figma scopesAC-6 Least Privilege; CSF PR.AA-05
Short-lived tokensLinear OAuth 24 hours, client credentials 30 daysIA-5 Authenticator Management
Admin restrictions on PATsAsana Manage apps (Enterprise+); Notion owner-only internal connectionsAC-6
Secret scanning with push protectionGitHub for all five, plus own scanning for Asana and AirtableCSF DE.CM-09; ATT&CK T1552.001 Credentials In Files
Audit log review for bulk readsEnterprise audit logsAU-6; ATT&CK T1213 Data from Information Repositories

Use of a stolen token maps to ATT&CK T1528 Steal Application Access Token and T1078.004 Cloud Accounts; containment is CSF RS.MI-01.

Small versus large organisations: a small team can keep a shared register of tokens and revoke by hand. A larger organisation should require OAuth apps or service accounts for any integration touching shared workspaces, use admin controls to restrict personal tokens, and add token revocation to the leaver process. See SaaS deprovisioning.

Where identity fits

A personal token turns a human identity into a non-human one that never signs in, never sees MFA and never leaves when the person does. Inventory these tokens as non-human identities with owners and expiry, and prefer platform-native service accounts so automation survives staff changes. AI assistants and agents connected to these workspaces deserve the same treatment: give each its own OAuth app or service account with the narrowest scopes, so its access can be reviewed and revoked without touching a person's account. See the API Keys vs OAuth Tokens Guide.

Common misconfigurations

  • Automation on a personal token: the integration breaks, or worse keeps running, when the person leaves.
  • "All workspaces and bases" Airtable grants: convenient at creation, and the widest possible leak.
  • Notion connections shared at the top of a page tree: sharing a parent page shares its children, widening what an internal token can read.
  • Linear OAuth apps in the main workspace: every admin there gains access to the app, against Linear's recommendation.
  • Rotating only the client secret: in Linear this leaves user access and refresh tokens valid.
  • Secrets pasted into work items: a single SaaS token then unlocks credentials for other systems.

Practitioner checklist

  • Inventory personal tokens, OAuth apps and service account tokens across Notion, Asana, Airtable, Linear and Figma.
  • Move integrations to OAuth apps or service accounts with minimal scopes and data.
  • Restrict who can create personal tokens and internal connections using admin controls.
  • Enable GitHub push protection and add your own scanning for Asana and Airtable tokens.
  • Export SaaS audit logs and alert on bulk reads, new integrations and new webhooks.
  • Revoke a leaver's tokens as part of offboarding, and confirm rejection.
  • Write a per-platform revoke runbook, including Linear's separate token revocation.
  • Scan workspace content for pasted secrets and rotate any found.
  • Remove tokens unused for 90 days.

Standards and references

Related NHI Mgmt Group resources: SaaS API Token Security Guide · Atlassian API Tokens Security Guide · Leaked Credential Response Playbook · OAuth Token Theft Incident Playbook

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 28 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.