Workspaces, projects & collaboration
Workspaces are how API Stash organizes your work and your team. Everything you create lives inside a workspace, and everything in a workspace is shared with its members.
Workspaces
A workspace holds everything: projects, collections, folders, requests, flows, environments, and history. It is the boundary for sharing, for billing, and for access control. Most teams keep a single workspace; larger organizations sometimes use one per team or product.
Members & roles
Every member of a workspace has a role:
| Role | Can do |
|---|---|
| Owner | Everything a member can do, plus manage members, manage billing, and delete the workspace. |
| Member | View and edit projects, collections, requests, flows, and environments; run flows and schedules; comment. |
The owner who created the workspace manages billing and membership; see Plans & billing.
Projects
Projects group collections within a workspace. Use them to separate, say, your public API from your internal services, or to keep each microservice's collections together. A project contains collections, which in turn contain folders and requests.
Inviting teammates
From workspace settings, invite teammates by email address. Each receives an invitation link; accepting it adds them to the workspace with the role you assigned. You can change a member's role or remove them at any time.
Comments & @mentions
Leave comments directly on a request to discuss a tricky payload, flag a bug, or capture context for the next person. Use @mentions to notify a specific teammate — they'll be alerted that they've been pulled into the conversation.
Versioned history & revisions
Every save creates a revision tagged with the author and a timestamp. This gives you a full audit trail of how a request or flow evolved.
- Diff any two revisions to see exactly what changed.
- Restore an earlier revision to roll back a mistake.
- History never expires — the complete timeline is always available.