Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Workspaces and Projects help you organize your work in Mavera. A workspace is the top-level container that holds projects, threads, personas, and other resources. Projects are subdivisions within workspaces for organizing related work.Workspace vs Project
| Aspect | Workspace | Project |
|---|---|---|
| Level | Top-level container | Nested under a workspace |
| Scope | Team, department, or client | Campaign, initiative, or product |
| Access | Role-based (owner, manager, editor, etc.) | Inherits workspace access |
| Budget | budget_alert, usage_limit | Can have its own limits |
| Resources | Members, projects, personas | Threads, generations, focus groups |
| Usage | Many APIs require workspace_id | Some APIs accept project_id |
workspace_id. Projects are used for organizing work and tracking usage at a finer grain.
Usage in Other Endpoints
Many Mavera APIs require or acceptworkspace_id (and sometimes project_id) to scope resources:
| Endpoint | Requires | Notes |
|---|---|---|
| Focus Groups | workspace_id | Required when creating a focus group |
| Files / Folders | workspace_id | Upload and organize files by workspace |
| Video Analyses | workspace_id | Scope analyses to a workspace |
| Brand Voice | workspace_id | Brand profiles belong to a workspace |
| Content Generation | workspace_id | Generations scoped to workspace |
| Meetings | workspace_id (optional) | Filter list by workspace |
| Mave threads | — | Threads can be associated with projects |
| Personas | — | Personas can be workspace-scoped (custom) |
GET /workspaces or find it in the dashboard URL when viewing a workspace (e.g. app.mavera.io/workspaces/ws_abc123).
Workspaces
Top-level containers for team collaboration with role-based access control
Projects
Organize threads, generations, and resources within workspaces
Team Members
Invite members with specific roles (manager, editor, viewer, etc.)
Budget Controls
Set usage limits and alerts for workspaces and projects
Workspaces
Listing Workspaces
Creating a Workspace
Updating a Workspace
Deleting a Workspace
Team Members
Member Roles
| Role | Description |
|---|---|
owner | Full control, can delete workspace |
manager | Manage members and settings |
editor | Create and edit content |
analyst | View and analyze data |
viewer | Read-only access |
creative_specialist | Create content with specific focus |
client_viewer | Limited external access |
department_admin | Department-level administration |
Listing Members
Inviting Members
Updating Member Role
Removing Members
Projects
Listing Projects
Creating a Project
Getting Project Details
Updating a Project
Budget Controls
Both workspaces and projects support budget controls to help manage credit usage.| Field | Description |
|---|---|
budget_alert | Credit threshold that triggers an alert notification |
usage_limit | Hard limit that prevents further usage when reached |
billing_email | Email address for budget notifications |
Best Practices
Organize by team or client
Organize by team or client
Create separate workspaces for different teams or clients to maintain clear separation of resources and access control.
Use projects for campaigns or initiatives
Use projects for campaigns or initiatives
Within a workspace, create projects for specific campaigns, products, or initiatives. This helps track usage and organize related work.
Set appropriate roles
Set appropriate roles
Assign the minimum required role to each member. Use
viewer for stakeholders who only need to see results, editor for content creators, and manager for team leads.Configure budget alerts early
Configure budget alerts early
Set
budget_alert thresholds to get notified before hitting limits. This gives you time to adjust or request additional credits.Workspaces API Reference
See the full API specification for Workspace endpoints
Projects API Reference
See the full API specification for Project endpoints