Hand off investigation context
Share goals, sheets, JOIN evidence, notes and plans with a colleague or assistant while preserving access boundaries.
SchemaMap 0.14.0 · Updated · The editor uses Russian UI labels, shown as written.
Who this helps
For teams changing assignees, reviewing work or returning to a task a month later. Start with a saved task containing clearly named sheets and findings. The recipient needs their own account with area access; an assistant needs its own permitted connection.
Preserve the meaning
- Check the task goal, tracker/MR links and recent journal entries.
- Save an Overview sheet and a separate detailed sheet.
- Check the common plan and JOIN evidence; distinguish hypotheses.
- Grant the appropriate role and share the link. Ask the recipient to explain the path from the starting table.
The result is reproducible shared context. If a file is needed, export reviewed JSON/PNG/SVG; exports do not transfer permissions or private conversations.
Conversations and personal state
A new chat does not inherit an old thread or its proof. Private discussion handoff requires explicit thread membership within owner permissions. Never send tokens in a message. Open tabs and camera are not imposed on your colleague. A web chat reads available replies during an active interaction; a finished chat is not automatically awakened.
Next: MCP, REST and AI integrations
Related materials: Areas, tasks, views and sheets · MCP, REST and AI integrations