How invites work
On any Builder or Studio project, you can invite teammates by entering their email addresses. Each person receives an invitation link and, once they accept, gains access to the project workspace. They log in with their own Marcus account—no shared credentials.
Invitations are sent immediately, and you can revoke access at any time from the project settings panel. There's no limit to the number of teammates you can invite on Builder or Studio plans.
What teammates can do
On the Builder plan, every invited teammate has full edit access. They can modify pages, adjust design tokens, upload images, edit content, and publish changes. This works well for small teams where everyone is trusted to make decisions.
Studio adds role-based permissions. You assign each teammate one of three roles: viewer (can browse and comment but not edit), editor (can edit and publish), or admin (full control including inviting others and billing). This granularity helps larger teams maintain clear ownership and avoid accidental overwrites.
Activity log and version history
Every Marcus project includes an activity log that records who changed what and when. You'll see timestamps, the teammate's name, and a summary of the action—edited a page, uploaded an asset, changed a design token. This transparency helps you track progress and troubleshoot issues.
The activity log is read-only. It's not a full version-control system like Git, but it gives you enough context to understand recent changes. If you need to revert to an earlier state, you can export the project as a ZIP at any point and restore from that snapshot.
Studio SSO for enterprise teams
Studio plans support single sign-on via SAML 2.0. This means your team can log in using your existing identity provider—Google Workspace, Microsoft Entra ID (formerly Azure AD), Okta, or another SAML-compatible service. SSO centralizes access control and makes onboarding and offboarding faster.
SSO is configured per organization, not per project. Once enabled, all teammates within your Studio account authenticate through your identity provider. You manage permissions and roles inside Marcus; the SSO provider handles login credentials.
Why the free tier doesn't support teams
The free tier is limited to one project and five pages, designed for individuals testing Marcus or building a simple personal site. Collaboration features—invites, activity logs, and role permissions—are available only on paid plans. This keeps the free tier focused and sustainable.
If you're evaluating Marcus with a team, the Builder plan at €29/month/project is the starting point. You get unlimited teammates, the activity log, and full editing rights for everyone.
Real-time editing and conflicts
Marcus doesn't yet support live collaborative editing like Google Docs. If two teammates edit the same page simultaneously, the last person to publish wins. The activity log will show both edits, but the earlier one will be overwritten.
To avoid conflicts, communicate with your team about who's working on what. Most teams establish a simple workflow: assign pages or sections to specific people, use the activity log to check recent changes before starting work, and export a ZIP backup before major updates. We're exploring real-time sync for a future release, but the current system works well for teams that plan their editing sessions.
Exporting projects for external collaborators
If you're working with freelancers, contractors, or clients who don't need ongoing access, you can export the project as a ZIP file containing all HTML, CSS, images, and assets. They can review the site offline, make changes in their own tools, and send the updated files back to you.
This workflow is common for design reviews or final client approval. The ZIP export is always up-to-date with the latest published state, so external stakeholders see exactly what your team built. You can re-import edited files manually or use them as a handoff package for deployment outside Marcus.