Skip to main content
Workspaces are the top-level organizational containers in PraisonAI Platform that hold projects, issues, agents, and team members. Workspaces are the top-level organizational containers in PraisonAI Platform that hold projects, issues, agents, and team members.
The user asks the agent to organise work; PlatformClient creates workspaces that hold projects, issues, and members.

Quick Start

1

Create Workspace

2

List Workspaces


How It Works


API Reference

Create Workspace

Creates a new workspace with the specified configuration.
Request:
Response:

List Workspaces

Retrieves paginated list of user’s workspaces.
Query Parameters:
  • limit (int): Results per page (default: 10, max: 100)
  • offset (int): Pagination offset (default: 0)

Update Workspace

Updates workspace properties using partial data.
Request:

Python SDK Examples

Basic Operations

Advanced Management

Workspace Deletion: Deleting a workspace now also removes all Member rows associated with it in the same transaction. Previously, memberships could be orphaned and surface in subsequent member lookups.

Key Concepts

URL-friendly identifier that’s auto-generated from name if not provided. Must be unique across the platform. Used for friendly URLs like /workspace/my-team.
Users can own or belong to multiple workspaces. Access control ensures users only see workspaces they have permissions for.
Flexible JSON dictionary for workspace-level configuration like themes, notification preferences, or feature toggles.
Workspaces → Projects → Issues/Agents/Tasks. Workspaces provide the top-level boundary for organizing work and team access.

Best Practices

Use descriptive names that reflect the team or purpose. Avoid generic names like “Workspace 1”. Good examples: “Marketing Team”, “Backend Services”, “Client Projects”.
Choose memorable slugs for URLs. Use hyphens, not underscores. Keep them short but descriptive: marketing-team not marketing_team_workspace_2024.
Use settings for workspace-wide preferences. Store user preferences separately. Common settings: theme, defaultProject, notifications.
Plan member permissions before inviting users. Consider using role-based access with workspace-level roles like owner, admin, member.

Testing

Test workspace operations to ensure proper functionality:

Projects

Organize work within workspaces using projects

Members

Manage team access and permissions