An AI assistant helped investigate and prepare this question for the account owner.
We are building a personal screenshot tool that each user deploys into their own Hobby account through Vercel Drop. We want normal provider sign-in/consent, without asking users to copy tokens or register an OAuth app.
Our isolated prototype works after manually connecting Blob, registering a public PKCE sign-in client with an exact callback, and configuring a verified owner user ID and app origin. We want to remove those per-install steps without letting the first public visitor claim ownership.
The Sign in with Vercel docs list Blob resource permissions as private beta; our App dashboard exposes only openid, profile, email and offline_access: https://vercel.com/docs/sign-in-with-vercel/scopes-and-permissions
We also reviewed the Integration route. Its registration form offers Integration Resource, Projects and Environment Variables permissions, but we cannot identify an explicit Blob scope: https://vercel.com/docs/integrations/create-integration/vercel-api-integrations
What is the supported Hobby consent route for a helper to:
- Create a Blob store and connect it to one user-selected Drop project? Which exact Integration scope/API permits this, or is Sign in with Vercel beta access needed?
- Verify the consenting user controls that project and handle sign-in callbacks for independently deployed app origins through a central helper?
- Do this without billing permissions or access to unrelated projects? Does it require provider enablement, marketplace approval or a paid plan?
A pointer to the supported architecture and permission mapping would help.