Work as a team · Lesson 17 of 20
Share a workspace with your team
Invite people with the right role, see who changed what, and decide how long data is kept.
A workspace holds collections, environments, API definitions, mocks, monitors and flows. Your account starts with a personal workspace; create more for teams or projects, and share them.
Invite people
- Open the workspace menu at the top left and click Manage, then choose the workspace.
- In Share, type one or more email addresses, pick a role and send the invitation.
Roles:
- Viewer: can open and send everything, but not change it;
- Editor: can create and change collections, environments and the rest;
- Admin: can also invite and remove people, change roles, settings and retention, and delete the workspace.
People get an email with a link that expires in 7 days. Pending invitations are listed so you can revoke them. Changes sync live: when a teammate saves a request, it updates on your screen, and if you both edit the same thing Swastik Codes asks which version to keep instead of silently overwriting.
For a whole team, create it under Teams and give the workspace team visibility; team roles then apply.
Review changes
Collections keep a version history: right-click a collection and choose Versions & merge to see earlier versions and restore one. To change a collection without disturbing everyone, fork it, make your changes and open a pull request (the Forks and Pull requests tabs of the same dialog) that teammates review and merge. Anyone can leave comments on a request.
The audit log
Admins can see exactly what happened in the workspace. In the workspace settings, under Audit and retention, click Open audit log:
- every save and delete of a collection, environment, API definition, flow, mock or monitor;
- invitations sent, accepted and revoked, members removed and roles changed;
- documentation published or unpublished, versions restored, items restored or deleted from the trash, and retention changes.
Each entry says who did it and when. Filter by kind, load older entries, and Download CSV for a spreadsheet or an auditor.
Decide how long data is kept
Under Audit and retention, admins can set how many days to keep request history, monitor runs and the audit log. Older data is deleted automatically every hour. Leave a field empty to keep it (the audit log defaults to 365 days).
Protect accounts
Ask everyone to turn on two-factor sign-in in Account → Security: they scan a QR code with an authenticator app, and password and GitHub sign-ins then need a code too. Keep the ten recovery codes somewhere safe.
What you learned
- Invite people as viewers, editors or admins; changes sync live and conflicts are never silently lost.
- Admins can read the audit log, export it as CSV, and set how long data is kept.
Next: publish documentation people outside the team can read.