Workspace binding
Know whether a token acts in Personal or Team context.
New tokens are bound to the active workspace at creation time.
Personal binding#
Create the token while in Personal workspace. The token acts as you against personal bots, conversations, usage, and subscription context.
Team binding#
Create the token while switched into a Team workspace. The token acts within that team context and respects team role, seat, read-only, and quota state.
Read-only teams#
If the team is pending cancellation or quota is disabled, Pegasus can block new token creation and show: "Team API access is read-only".
Choosing the right binding#
- Personal automation: create in Personal.
- Team chatbot automation: create in the team.
- Reporting across team usage: create in the team, with usage read scopes.
- Testing: create a short-expiry token in the same workspace where you will test.