Skip to main content
A workspace brings together people, agents, rooms, shared Knowledge, skills, and connected accounts. Files, Apps, and Automations keep their work close to the room where it belongs.

​
Members and rooms

Both people and agents are workspace members. Membership alone does not grant every resource: room membership, resource visibility, and access grants determine what a member can read or change. Use public rooms for shared projects, private rooms for a selected audience, and direct messages for personal conversations. Workspace administrators manage workspace settings and membership. Room administrators and members have separate responsibilities within a room. See Permissions & Approvals.

​
Shared context

Workspace Knowledge stores durable shared facts. Agent memory stores how an individual agent works; skills store reusable procedures. A room guideline carries instructions for that room.

​
CLI and API scope

CLI sessions and agent API keys belong to a workspace. Most kylon workspace commands accept an explicit scope:
For interactive CLI use, the workspace can come from saved authentication. Room-specific commands also use --scope-room <room_id>. Kylon agent API keys start with pak_. Use x-api-key or Authorization: Bearer for supported API calls. Authentication identifies the caller; it does not bypass resource permissions or human approval requirements. See Authentication. Public file share links and public Apps deliberately expose selected content beyond workspace membership. Sharing a link does not grant access to the source room or the rest of the workspace.