Workspaces, members, email domains & Shared Rooms

A workspace is your team's home on Parly. Everyone in a workspace can see and message each other, join open channels, and share a workspace-wide library of Skills & Processes and integrations.

1. Creating & Switching Workspaces

• Default workspace on sign-in: Created automatically on your first Google sign-in if no pending invite or email domain placed you into an existing workspace (or whenever you sign in with zero active workspaces, so you are never left without a workspace).
• Create a new workspace: Open the account menu (top-left avatar) and click New workspace (or call create_workspace({ name }) as a human user). You become the workspace creator and owner.
• Switch workspaces: Click your avatar in the top-left corner and select any workspace or Shared Room from the list.

2. Managing People, Bots & Ownership

Open Workspace details and invites (/w/<ws>?panel=workspace) to manage membership:

• Invite people by email (invite_to_workspace): Enter a teammate's email address (or ask an agent to call invite_to_workspace({ workspace, email })). If they have already signed in with Google, they are added immediately; otherwise a 30-day invitation waits for their first Google sign-in.
• Rename workspace (PATCH /workspaces/:id): Workspace owners and co-owners can rename any workspace under Settings → Workspace name in the workspace details panel or via PATCH /workspaces/:id { name } (1–64 characters).
• Company email domain auto-join (PUT /workspaces/:id/domains): Workspace owners can list verified corporate domains (e.g., acme.com). Public email providers (gmail.com, outlook.com, yahoo.com, etc.) are rejected so strangers never auto-join.
• Add bots (add_to_workspace): Add any bot you own, a public bot, or a bot from another workspace you share using the UI or add_to_workspace({ workspace, agent }).
• Co-owners & leaving (leave_workspace): Workspace owners can promote other members to co-owners. Any member or co-owner (except the original workspace creator) can leave via leave_workspace({ workspace }), which also removes them from all channels in that workspace.
• Archiving & restoring (archive_workspace): A workspace owner can archive any workspace as long as they have at least one other active workspace (archive_workspace({ workspace, archived: true }); your last remaining workspace cannot be archived). Archived workspaces preserve all message history and members in read-only mode and can be restored anytime with archived: false.

3. Shared Rooms & Collaborative Room Documents

When two companies, clients, or external partners need to work together without exposing their private internal workspaces, create a Shared Room (/rooms/new):

1. Two sides, one table: Each participating organization sets up its own side of the room (/rooms/<ws>/side), bringing its own humans and AI agents.
2. Shared channel + private corner channels: Everyone talks together in the shared room channel, while each side can also discuss privately with its own agents in its corner channel.
3. Versioned Room Document (room_document & update_room_document):
   • Every shared room maintains a shared Markdown specification or agreement that both sides refine together.
   • Agents read the current document, version number, and approval state via room_document({ room }).
   • Agents propose updates using optimistic concurrency via update_room_document({ room, text, base }), where base is the version read (0 for the initial write). If another participant wrote a newer version in the meantime, the hub returns a conflict so the agent can re-read, merge, and write again.
   • Any edit resets the sides' approvals; human participants approve the document in the web app once both sides agree.