Workspaces
A workspace is a shared environment that contains everything a team builds and uses together — chatflows, agentflows, document stores, tools, credentials, PebbleChat conversations, and the people who have access to it.
Every user belongs to at least one workspace. Every asset belongs to exactly one workspace (unless it has been explicitly shared). This is the unit of collaboration in PebbleAI.
What a workspace contains
- Members and their roles — who has access and what they can do
- PebbleFlows assets — chatflows, agentflows, assistants, document stores, tools and variables
- PebbleChat history — conversations can be scoped to the workspace so colleagues can pick up where you left off
- Credentials — workspace-level API keys and OAuth connections used by shared flows
- Starter prompts — workspace-defined suggestions that appear on the PebbleChat landing page
- Ambient context — the workspace layer of the ambient context system
- Usage & observability data — every trace, every dollar, scoped to the workspace
Why it matters
Because everything in PebbleAI is workspace-scoped, you can be a member of multiple workspaces at once and see a completely different view in each one. Your credentials, flows, conversations and ambient context are all isolated — you switch workspaces and the app re-orients.
This is what enables multi-team PebbleAI deployments: Marketing can build their chatflows, Legal can build theirs, and neither sees the other’s data unless they explicitly share an asset.
Workspace roles
Within a workspace, every member has a role:
| Role | Can do |
|---|---|
| Workspace Admin | Everything below, plus manage members, edit workspace settings, and share assets outside the workspace |
| Editor | Create, edit and run flows, document stores and tools; use PebbleChat with full capabilities |
| Contributor | Use existing flows and PebbleChat; cannot create or edit workflow assets |
| Viewer | Read-only — see shared flows and conversations but cannot run or edit them |
Your workspace role is separate from your organisation role — see Organisation Admin → User Management for the organisation-level picture.
Organising workspaces
There is no single correct way to organise workspaces, but these patterns are common:
By department
Marketing · Sales · Support · HR · EngineeringBy project
Q4 Campaign · Product Launch · Customer OnboardingBy use case
Content Creation · Data Analysis · Internal AutomationFor most organisations, department-based workspaces work best because they map to how people think about who owns what. Project workspaces make sense when you have a defined end date and want to archive everything together.
Shared vs private
By default everything you create in a workspace is visible to every member of that workspace. If you need finer control:
- Ask your organisation admin to set up Asset Sharing & Permissions so specific assets can be shared across workspaces with controlled permissions.
- Use Private credentials (at the user level, not workspace level) for secrets you don’t want teammates to see.
Where to next
- Workspace Switcher — How to move between workspaces
- Organisation Admin → User Management — Who can be invited to a workspace
- Organisation Admin → Asset Sharing — Sharing flows and tools across workspaces