Collaborators

A collaborator space brings two approved Ramphearth workspaces together. Both sides keep their own membership and settings. The referral programme is still Partner program, at /partner.

Open Collaborators beside Clients, or its section in Chats. The destination appears when your plan includes Collaborators and you can open a space, or you are an Owner or Admin who can start one. To start, choose a category and Review and invite. Review the channels and privacy terms, enter the reason, and send an invitation or make a one-time code. Accepting and starting still require account confirmation. Existing /shared-categories links redirect to Collaborators, keeping their invitation details.

Each space opens on Conversation, Internal notes, Files, Contracts, Tasks, and Timeline. Additional channels stay available as additional tabs. Internal notes belong to your workspace alone, including when you join a space hosted by another workspace. Choose Discuss internally on a shared message to quote it into your team's notes. The other workspace cannot open those notes, their files, or their task board.

The shared Tasks tab offers people admitted on either side, by name. New task titles, descriptions and column names use the strictest word filter of both sides and are sealed in encrypted workspaces. A paused or ended conversation refuses task edits. Ending a space keeps its existing freeze and copy behaviour; shared tasks are copied under the receiving workspace's key. Internal notes stay in the workspace that owns them.

The Timeline currently lists recent shared conversation activity. The Contracts tab is reserved for the contracts feature. It displays an empty state until that feature is connected.

Existing API names

The product name changed; stored names and session API paths did not. Existing /org/:orgId/shares, /shares/accept, /shares/lookup, and shared_category.* audit names keep working. No new /v1, app-token, MCP, webhook or third-party access to shared channels is granted.

The authenticated category listing adds shareId to a visible collaborator category. Its workspace-owned notes channel has collaboratorRole: "internal"; channels that actually cross the share carry collaboratorRole: "shared". A local-only channel is never selected as the shared Conversation. Internal notes are never returned to the other workspace. Shared board responses add people: [{ id, name }] for the assignee picker and return assignees without email addresses. The new session route POST /org/:orgId/shares/channels/:channelId/discuss accepts { messageId } and returns { channelId, messageId } for the note posted in the requesting workspace. Both channels are checked again on the server.