Skip to content

Share a project and get comments

In shortViewers can view and comment. Editors can build, edit code and restore versions. Project Admins can also publish and manage the project. Invite people you trust. Only the project owner can grant, change or revoke Project Admin access.

Viewers can view and comment. Editors can build, edit code and restore versions. Project Admins can also publish and manage the project. Invite people you trust.

This is different from publishing: a published app is public, while a shared project shows the workspace — preview, code and chat — to the people you invite.

Can build, publish, unpublish and manage this project, including its data, users, secrets and integrations. Can manage Viewers and Editors. Only the owner can grant, change or revoke Project Admin access, transfer ownership, permanently delete the project, change account billing or buy domains. Usage follows the owner’s plan.

Project Admins can sync a GitHub repository already linked to the project. Linking or unlinking repositories and managing personal account connections remain owner controls. Domain purchases and renewals also remain owner controls.

Project Admin is a MonstarX project role, separate from an admin user inside your app. Grant it through Share. Making someone an app admin does not give them access to the MonstarX project.

Project Admins also have all Editor permissions: build requests, code editing, restoring versions and editing the request queue. Preview editing tools are available to the owner, Editors and Project Admins. Viewers can view and comment.

Can view & commentCan editProject AdminOwner (you)
See the preview and use the app in itYesYesYesYes
Read the code and the whole chatYesYesYesYes
Leave comments on the previewYesYesYesYes
Send requests (Build, Plan, Chat), use Edit mode and ClipNoYesYesYes
Edit code, change the feature plan, manage the queueNoYesYesYes
Restore a versionNoYesYesYes
Turn comments into features or dismiss themNoYesYesYes
Admin, Backend (data, users, secrets), Logs, Security, SEO/GEO, Social, QANoNoYesYes
Publish, unpublish, export, project settings and Viewer/Editor sharingNoNoYesYes
Grant/change/revoke Project Admin, transfer ownership, permanent deletion, billing and domain purchasesNoNoNoYes

Requests an editor sends count against your plan, because the owner’s plan pays for the project. Editors’ requests run in order with yours, always on the latest version of the app.

Admin features depend on the owning account’s availability. Removing or demoting an Admin stops new protected requests and closes their private build stream.

  1. Open your project and click Share in the workspace header.

  2. Type their email address.

  3. Choose Can view & comment, Can edit or Project Admin. Only the owner can choose Project Admin.

  4. Click Invite.

MonstarX emails them a link. The link works for 14 days, and only for that email address — forwarding it to someone else does not let them in. You can also click Copy link and send it yourself.

You can share a project with up to 20 people (people with access and open invites together). The list shows the count, for example 2 of 20 people invited.

  1. They open the link in the email. It shows who shared which project and what they will be able to see.

  2. They click Sign in to view, or Create an account for a free one, with the invited email address. The page shows part of that address, so they know which one to use. Afterwards they come back to the invite.

  3. They click View the project, and the project opens.

An invite for Can edit says so: Its code, ready for you to edit and You can send requests, edit code and restore versions.

If they are signed in with a different address, the page says which address the invite is for and offers Switch account:

The invite page also explains when a link has expired, was withdrawn, or was already used.

A viewer’s workspace has the Preview and Code tabs, Versions (to look, not restore) and a badge such as View & comment · shared by Alex Morgan. Where you have the prompt box, they see a note with a Comment on the preview button.

They follow the build as it happens — the chat, the feature plan, the preview updating — without refreshing. Some details stay private: they do not see rows from your database, the preview’s server logs, or live links to QA browsers.

An editor sees the same tabs, a Can edit badge, and the full prompt box, with Edit and Clip on the preview.

Anyone with access — you, viewers, editors and Project Admins — can leave a comment pinned to a spot in the preview.

Point at the button, say what should change.
  1. Click Comment on the preview (under the chat), or Comments in the preview’s toolbar and then New comment.

  2. Click an element or draw a box on the page to point at what you mean. Or skip this for a general comment.

  3. Write what should change — up to 2,000 characters.

  4. Click Post comment.

Each comment remembers the page it was on and the element it points at. The Comments button shows how many are open. A viewer can Withdraw their own comment while it is open, and can have up to 30 open at once.

When someone comments, you get a notification on the devices where you allowed them, and an email. Both open the preview with the comments showing. To avoid a flood, you are only told about a comment when nobody else commented in the 15 minutes before it; the rest simply wait in the list. See Notifications.

For each comment:

  • Turn into feature — edit the Feature title and click Add to plan. It goes on the feature plan with the page and element it points at, so MonstarX knows exactly where to make the change. Nothing is built until you ask.

  • Dismiss — close it without action. Dismissed and planned comments move under Reviewed, where you can Reopen a dismissed one.

How do I change or remove someone’s access?

Section titled “How do I change or remove someone’s access?”

Open Share (or SettingsPeople):

  • Change access — pick Can view & comment or Can edit next to their name.
  • Remove — click Remove, then Remove? to confirm. They lose access at once.
  • Resend — sends a pending invite again with a new link (the old link stops working).
  • Withdraw (the × next to an invite) — the link stops working.

Inviting someone again or clicking Resend makes a new link — at most once a minute and five times per invite. MonstarX sends up to 20 invite emails a day for you; after that the invite is still made and you copy its link to send yourself.

On the invited person’s Projects page, with their own projects, marked Shared (Can edit for an editor, or Project Admin for an admin) and By the owner. The Shared filter shows only those.

To stop following a project, they open its ⋯ menu and choose Leave project. The owner would have to invite them again.

Does the person I invite need a paid plan?

No. They sign in, or create a free MonstarX account, with the invited address. Requests an editor sends count against the owner's plan.

Can a viewer see my database or secrets?

No. Viewers and editors see the preview, the code and the chat, but not the Backend, logs, secrets or settings. Rows from your database are hidden in the chat too.

Can someone I share with publish the app?

Project Admin: Can build, publish, unpublish and manage this project, including its data, users, secrets and integrations. Can manage Viewers and Editors. Only the owner can grant, change or revoke Project Admin access, transfer ownership, permanently delete the project, change account billing or buy domains. Usage follows the owner’s plan.

How many people can I share a project with?

Up to 20, counting people with access and open invites.

The invite email did not arrive. What now?

Click Resend, or copy the link from the Share menu and send it yourself. It only works for the invited address.

Can I share the live app instead?

Yes — publish it and send the link. Anyone can use a published app. See Publish your app.