docs: clarify project membership as a trust boundary for auth#1089
Merged
Conversation
Reinforce that Arcade's default OAuth apps only work with the Arcade user verifier, which requires each end user to be a signed-in member of the project. This ties end-user authorization to project membership by design, so default OAuth apps are for development/single-tenant use and production multi-user apps should use their own OAuth app plus a custom verifier. - glossary: note that a project is a trust boundary whose members share access to its users, brokered tokens, and secrets - secure-auth-production: clarify (and strengthen) both verifier callouts to make the Arcade-verifier + project-membership requirement explicit Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
evantahler
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Clarifies how project membership relates to authorization, so readers understand the trust boundary a project represents.
Changes
resources/glossary— the Project entry now states that a project is a trust boundary: its members (and API-key holders) share access to its users, brokered tokens, and secrets, with guidance to only invite/join projects you trust.guides/user-facing-agents/secure-auth-production— both verifier callouts clarified: the Arcade user verifier requires end users to be signed-in project members, which is why default OAuth apps are for development/single-tenant use, while production multi-user apps should use their own OAuth app plus a custom verifier.Not changing the Google provider page — this behavior is generic to all default OAuth apps.
Notes for reviewers
Vale's advisory PR reviewer can't parse
secure-auth-production.mdxdue to a pre-existing nested-Tabsquirk; not a regression, and it doesn't fail CI.🤖 Generated with Claude Code