[Docs] Add note on limitation of organization scope on API tokens #859
Description
Topic: Understanding the nuances of Cloud’s REST APIs and API token scope
Purpose: Help users understand the difference between API Tokens and User Sessions. Cloud API Tokens are not org-scoped, but are user-scoped. This is a noteworthy caveat to include in the API documentation, so that users understand how they can explicitly control the use of their API tokens with respect to organizational boundaries.
Applicable to: This note is of import to users who belong to multiple organizations, not to users with membership to only a single org.
Tip: Include ad informational note that readers can relate to: draw upon the similarities of how GitHub Personal Access Tokens work
Example: Include an example of how to create a new design with organization and workspace specified. Through layer5-current-orgid or setting the selectedWorkspace and selectedOrganization preference for user through the preferences api
Add this documentation on the API Token page
Contributor Guide and Resources
- 📚 Instructions for contributing to documentation
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack