Your whole team, one workspace, no accidents.
Invite teammates with a shareable link, give each one the right level of access, and see exactly who created, deleted, or restored what — without anyone stepping on anyone else's work.
Access that matches what someone actually needs.
Three things a shared workspace replaces.
Three roles, enforced everywhere
Owner, Editor, and Viewer — every collection, folder, request, and environment endpoint checks the role before it lets an action through, not just the UI.
Invite with a link, not a support ticket
Generate a shareable invite link with a role already attached, optionally email it directly, and set it to expire — no back-and-forth to get a teammate access.
An activity log, not a guessing game
Every collection, folder, request, and environment change is recorded — who created, deleted, or restored it, and when — so "who changed this?" has an actual answer.
Team Workspaces, answered.
The practical questions before you invite your first teammate.
What's the difference between the three roles?
Owner has full control including membership and workspace settings, Editor can create and modify collections/requests/environments, and Viewer can see everything but not change it. Every one of those boundaries is enforced on the API itself, not just hidden in the UI.
Does an invite have to go through email?
No — creating an invitation generates a shareable link with a role already attached, which works whether or not you send it by email. If a mail delivery fails for any reason, the link itself still works.
Can an invite expire or be revoked?
Yes — invitations can be created with an expiration window, and a pending invitation can be revoked at any time before someone accepts it.
What actions actually show up in the activity log?
Creating, deleting, and restoring collections, folders, requests, and environments — each entry records which teammate did it and when.
Talk to us.
Tell us about your team and what you're building. We'll get back to you.