Learn how to collaborate with your team on mock API projects with role-based permissions, invitations, and organization linking.
Workspaces and organizations are live. Create workspaces from the dashboard, invite members with Owner/Editor/Viewer roles, and link workspaces to organizations at /organizations.
Configure workspace alert rules (error rate, latency, request volume) with optional per-rule email addresses in workspace settings.
From a workspace project's Settings → Sharing tab, use the link to open workspace member management.
Enterprise SSO for organizations: Enterprise SSO guide.
Invite team members to your workspace using their email. Manage all your shared mock projects in one unified dashboard.
Control who can view, edit, or manage endpoints. Define granular access levels for developers, testers, and stakeholders.
Complete control over the workspace, including member roles, invitations, and project/workspace deletion.
Can create, modify, and delete endpoints and projects within the workspace, and can invite or remove Editors/Viewers (but not Owners).
Can browse projects, test endpoints, and see the member list, but cannot make any changes.
Owners and Editors can invite a teammate from the Members tab of a workspace: click Invite Member, enter their email, and choose a role. If the email already belongs to a registered user, the existing in-app invite path still works.
If the email is not registered yet, Mock API Builder opens the creator's mail client with a prefilled invite and also offers a copyable accept link. The platform does not send this invite email through Mailgun for this path.
The invite preview shows only the masked recipient email. Pending email invites grant no workspace or project access until accepted, and Managers can copy the invite link or revoke the pending invite from the member list.
When you have a pending invitation, open the accept link at /invite/accept?token=.... If needed, you'll be prompted to log in or register first, then returned to accept the workspace invite.
Registered users can also accept invitations from the Pending Invitations card at the top of /workspaces showing the workspace name, the role you've been invited as, and who invited you — with Accept and Decline buttons.
Registered-user invites remain in-app. Unregistered email invites rely on the creator's mailto client or copied accept link, so no platform email is sent for that path.
An organization sits above your workspaces: Organization → Workspaces → Projects. Use one when you need a single member roster or enterprise SSO across several teams. A standalone workspace is enough for most teams — organizations are optional.
Unlike workspace invitations, adding someone to an organization is immediate — there's no pending state. They must already have an account.
From an organization's detail page at /organizations, pick one of your unlinked workspaces from the dropdown and click Link workspace. It now appears under that organization's workspace list.
Only the current owner can transfer ownership, and only to an existing member of the organization. From the member list on the organization's detail page, open a member's menu and choose Transfer Ownership. Once confirmed, that member becomes the owner and you're downgraded to Editor — the transfer can't be undone from the UI, the new owner would need to transfer it back.
