Shared Conversations
AI work belongs to the team.
Bring teammates into the same bot thread with preserved identity, roles, audit trails, and linked artifacts.
Continuity under pressure
No more holiday handoff archaeology.
A private copilot works until the person who drove the work is out for a holiday, sick day, or urgent customer call. Then the team has to rebuild the prompt history from memory, screenshots, and forwarded files.
Shared Conversations make the handoff explicit. The covering teammate can open the same bot thread, see who asked what, inspect the linked task and files, and continue without pretending to be the original user.
Demo requester created the conversation
Demo manager was added as editor
Finance reviewer was added as viewer
Supplier spreadsheet was attached
Workforce task BY-214 was linked
Access change was recorded in audit
Private copilots versus team-owned AI
Keep the work where the team can govern it.
Private copilot history
- Work disappears into one employee's account history.
- Managers ask for screenshots or forwarded snippets to reconstruct context.
- Holiday coverage depends on the original owner being available.
- Identity, approvals, and artifact links are hard to verify later.
Botyard Shared Conversation
- The same bot thread is available to the authorized team.
- Each person appears as themselves with preserved identity.
- Handoffs keep prompts, assumptions, files, decisions, and tasks together.
- Audit and export paths make the work reviewable after the moment passes.
Permissions and roles
Share the thread without sharing the account.
Shared Conversations combine bot policy, organization roles, and conversation-level permissions. The result is a shared workspace for AI work that still knows who each person is and what they are allowed to do.
Conversation roles
Grant owner, editor, or viewer access at the conversation level so sensitive work does not require account sharing.
Org policy
Bot and organization roles still apply, keeping shared work inside the boundaries your admins already manage.
Change membership
Add a teammate when they join the workstream, remove them when they rotate off, and keep the thread intact.
Auditable actions
Messages and access changes are tied to the person who performed them, not a borrowed login or generic bot account.
Access panel
Holiday operations handoff
Maya
Demo requester
Jon
Demo manager
Finance Review
Added for approval
Policy check
Bot role, organization role, and conversation permission all match before the handoff thread opens.
Capabilities
Conversation context, permissions, and artifacts in one place.
Shared work, separate people
- Multiple users can access the same bot conversation.
- Original user identity is preserved on messages and actions.
- The bot sees one multi-user thread instead of scattered private histories.
- No password, browser profile, or account sharing is required.
Governed access
- Bot and organization roles control who can open the conversation.
- Conversation-level permissions define who can view, contribute, or manage access.
- Users can be added or removed later as responsibilities change.
- External guest access can be scoped through enterprise onboarding.
Evidence that travels
- Audit trail records user messages, access changes, and important actions.
- Conversations can link to Workforce tasks, PRs, reviews, files, and Bot Pages where implemented.
- Exportability helps teams preserve decisions outside a single chat window.
- Retention requirements can be scoped through enterprise onboarding.
Start with a shared thread
Make AI work reviewable before it becomes business-critical.
Give every governed bot conversation a team owner, clear permissions, preserved identity, and an audit trail your organization can trust.
Get Started