Hub Cloud · Access
A useful app deserves to be shared.
Share with your team, invite a client, or open it to everyone. Hub handles sign-in for protected apps. New apps start with organization access.
Choose the audience.
Set access per instance without rebuilding. Choose one mode; each command changes only that instance.
App invitations cover every instance. Organization roles separately control deployment, logs, and settings.
Inspect with hub app my-app access. Use my-app/staging for another instance.
# Organization members and app invitees
hub app my-app access org
# Invite someone to your organization
hub invite team@example.com# The organization owner and app invitees
hub app my-app access private# Anyone with the URL, without sign-in
hub app my-app access publicInvite someone to one app.
Give someone access without organization membership or deployment controls. Share the returned invitation link yourself.
Hub does not email app invitations or expire them automatically. Keep links private; use hub app my-app uninvite person@example.com to revoke one.
hub app my-app invite person@example.comUse identity when you need it.
Your server can receive the person’s email, name, and role after Hub approves a protected request. Public apps receive no identity headers. Your app decides what each person can do.
Use identity in your app →Current hosted password sign-in does not verify email ownership. Clerk can verify browser email when configured. Review the access and invitation boundaries.