Advanced
Workspaces
Team workspaces, roles and collaboration
Workspaces let a team manage listings, releases, agents, and revenue together — with roles, shared billing, and an audit trail. Solo creators can ignore this; teams should set it up early.
Structure
Workspace
├── Members (with roles)
├── Listings (apps, web apps, agents)
├── API keys (shared, scoped)
├── Billing & payouts
└── Audit log
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing & deleting the workspace |
| Admin | Manage members, listings, releases, keys |
| Publisher | Create/edit listings and publish releases |
| Analyst | Read analytics and finance |
| Billing | Manage payout methods and invoices |
Grant the least role that lets someone do their job.
Invite a member
curl -X POST https://api.theaimart.co/api/v1/workspaces/$WS_ID/members \
-H "Authorization: Bearer $THEAIMART_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "dev@yourco.com", "role": "publisher" }'
Workspace API keys belong to the workspace, not a person — so integrations keep working when a member leaves. Personal keys are revoked when their owner departs.
Audit log
Every sensitive action (release published, payout method changed, key created) is recorded with actor, time, and detail. Export it for compliance or incident review.
Best practices
- •Separate prod and staging keys; restrict prod publishing to Admins.
- •Require the verification badge on the workspace's public developer page.
- •Review the member list and audit log on a regular cadence.