---
title: "Scope your Personal Access Tokens"
description: "Supabase now scopes Personal Access Tokens to specific resources and permissions, limiting what each token can do. Announced at Supabase Select on October 2 after becoming generally available on September 28, the feature lets you choose resources such as a single project, permissions such as read-only database access, and an expiration date up to one year. The token’s scope is fixed at creation, and its effective permissions are bounded by the user’s own role; losing access revokes the token’s ability until restored. A review screen shows the blast radius with a risk banner, and scoped tokens start with the prefix sbp_fc. Existing full-access tokens remain unaffected and carry a Legacy badge, while the Dashboard now creates scoped tokens by default, with nearly nine out of ten new tokens scoped."
---

# Scope your Personal Access Tokens

[Supabase](https://yomu.fyi/company/supabase) · hieu, kemal\_y, gildas\_garcia, wenbo · Oct 26, 2026

**Type:** Announcement

## Summary

Supabase now scopes Personal Access Tokens to specific resources and permissions, limiting what each token can do. Announced at Supabase Select on October 2 after becoming generally available on September 28, the feature lets you choose resources such as a single project, permissions such as read-only database access, and an expiration date up to one year. The token’s scope is fixed at creation, and its effective permissions are bounded by the user’s own role; losing access revokes the token’s ability until restored. A review screen shows the blast radius with a risk banner, and scoped tokens start with the prefix sbp\_fc. Existing full-access tokens remain unaffected and carry a Legacy badge, while the Dashboard now creates scoped tokens by default, with nearly nine out of ten new tokens scoped.

## Context

Personal Access Tokens previously granted full account access. Supabase introduced scoping to limit tokens to specific projects and permissions, announced at Supabase Select on October 2 after becoming generally available on September 28.

## Approach / What changed

Create a token in the Dashboard by selecting resources (e.g., a single project), permissions (e.g., database read), and an expiry date. The token gets the prefix sbp\_fc and can be used with the Management API, MCP server, or CLI via bearer authentication. Existing tokens remain unchanged.

## Takeaways

- Scoped tokens are created in the Dashboard by selecting resources, permissions, and an expiry; the token’s scope is fixed at creation.
- A token’s effective permissions are bounded by the user’s own role; losing access to a resource revokes the token’s access until restored.
- Existing full-access tokens remain unaffected and carry a Legacy badge; the Dashboard now creates scoped tokens by default, with nearly 90% of new tokens scoped since launch.

## FAQ

### Can I still create a token with full account access?

Yes, the Dashboard still offers a 'Create legacy token' option for workflows that need full access, but all new tokens are scoped by default.

### What happens if my access to a project is revoked for a scoped token?

The token loses that access until your access is restored. The token's detail view marks any resource you can no longer reach.

### How do I use a scoped token with the Supabase CLI?

Create the token in the Dashboard and pass it with \`supabase login --token <token>\`. For CI, set the SUPABASE\_ACCESS\_TOKEN environment variable; it overrides locally saved tokens.

**Tags:** [Authorization](https://yomu.fyi/topic/authorization), [Personal Access Tokens](https://yomu.fyi/topic/personal-access-tokens), [Security](https://yomu.fyi/topic/security), [Supabase](https://yomu.fyi/topic/supabase)

- Source: [Supabase](https://supabase.com/blog/scope-your-personal-access-tokens)
- Source URL: https://supabase.com/blog/scope-your-personal-access-tokens
- Ingested by Yomu: 2026-10-26T21:00:13.228Z

[Read original post](https://supabase.com/blog/scope-your-personal-access-tokens)
