Builder team access
People who help you build the app are collaborators, not end users. Customers belong under End-Users, not as collaborators.
Invite from App Settings (team sharing). Confirm they can open the app with the expected collaborator role, and that they do not appear as a portal end user unless you also invited them there. Remove access from App Settings when they leave the project. Collaborators can also leave themselves from App Settings → Access. The invitee must verify their email before they can accept. Invite links last 7 days by default and never more than 30 days.
Any Owner or Admin on the app can cancel a pending invite, not only the person who sent it. If you remove someone’s collaborator access (or change them from Admin to Editor or Viewer), pending invites they sent for that app are cancelled. The same applies for organization invites when you remove an org Admin or Owner, or change them to Member.
Only add someone as a collaborator if they should change (or review) the blueprint. Example: invite an Editor so they can change the app with you, but not billing.
If the app owner has the Builder MCP add-on, Editors and Admins can connect an MCP client to that app. Creating a new app from the client still requires the add-on on the creator’s own subscription. Adding another project on an existing app needs Admin on that app. See GenieForge Builder MCP.