Share a Matrix.page app by email
Preview the planned email-invitation flow for Matrix.page apps. Invitations remain disabled while sign-in and email delivery are qualified.
Maintained by the Matrix OS team. Product instructions are updated with the supported workflow.
Not available yet
Email invitations remain disabled. Sign-in and email delivery are still being verified, and the Invite by email control in Share → Private is unavailable. This page describes the planned experience after rollout. Public publishing remains available; existing private one-time links continue until their normal expiry, but new ones cannot be created.
After rollout, email invitations will let you give specific people access to the visitor version of a published app. The app stays yours. The planned sign-in flow uses the app's permanent matrix.page URL and the same Matrix account recipients use at the main Matrix site. It is intended to reuse an existing session, or let recipients sign in or create an account on the app's Matrix.page URL. Google or GitHub authentication may temporarily open the provider and must return to the same app. Matrix onboarding, billing, and computer provisioning are excluded from this flow. These account flows still need verification before invitations become available.
Matrix checks the account's verified email addresses against the active invitation list. A matching primary or secondary address gives that account access to this app. Receiving or forwarding the invitation email alone does not grant access. An unverified address or a different account cannot open the app.
Opening a shared app does not start Matrix onboarding, billing, desktop setup, developer-tool selection, or computer provisioning. Those flows belong to the main Matrix experience.
Choose an access mode
| Mode | Who can open the app | How access works |
|---|---|---|
| Public | Anyone | Open the published URL. |
| Existing private one-time links (legacy) | A browser that claims an existing, unexpired link | No account is required. New links and new publications in this mode are unavailable. |
| Email invitations (planned) | Invited Matrix accounts | A verified account email must match an active invitation. This mode is currently disabled. |
An app has one Matrix.page access mode at a time. Switching away from email invitations revokes email viewer access. Switching back does not restore old grants; invite people again as needed. A one-time link is never treated as an email identity.
Planned invitation controls after rollout
- Open the app's Share popover and choose Private.
- Enter an email address in Invite by email, then choose Invite. If the app uses public access or one-time links, confirm the switch to invite-only access. This ends access from the previous mode.
- Review whether the invitation was queued or already exists. Repeat for another person as needed. The invitation list shows pending, accepted, expired, revoked, and delivery states; queued does not mean the email has arrived.
- If delivery fails, its status is unknown, or an invitation expires, use Resend when offered. You can revoke a pending or accepted invitation at any time. Use Load more invitations for older records or Show newest invitations to return to the latest list.
- Use Copy link to share the canonical Matrix.page app URL directly with invited people. The link itself does not grant access; they still need a matching verified Matrix account.
After opening the app, recipients can choose Sign out in the Matrix.page account bar. It ends that browser session's shared-app authority before signing out of Matrix and returns to the same app's sign-in page. If an account does not match an invitation, Use another account is available on the access page. These flows remain subject to the sign-in rollout checks above.
Invitations expire after seven days if they are not accepted. After acceptance, access is tied to the recipient's stable Matrix account identity, so a change to the account's primary email does not by itself remove an already accepted grant. The recipient can return in another browser by signing in with the same account. An owner revocation, account inactivation or deletion, access-mode change, or unpublish blocks subsequent app requests. A browser may retain content it already downloaded.
What recipients can do
Recipients get only the visitor behavior you declared when publishing: the reviewed app build, declared public data, and declared visitor forms or actions. Form responses are stored in your owner-controlled PostgreSQL database and remain under your ownership.
Recipients cannot view app source, clone or republish your app, open owner submissions or publishing controls, access your private runtime or database, use private Matrix tools, read credentials, or transfer ownership. The same visitor limits apply to public and one-time-link publishing.
For build and visitor-form setup, see Publish an app as a website.
How is this guide?
Workspace Canvas
Organize PRs, terminals, and review loops in Matrix OS Workspace Canvas. Learn how spatial workspaces connect project work and running sessions.
Onboarding Launch Readiness
Learn how Matrix prepares a founder or developer workspace before paid access, including readiness checks and the handoff to a running computer.