> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/task-management/sharing-plans-and-trackers.md). # Sharing Plans and Trackers For the complete team workflow, including shared boards, collaborative item bodies, comments, history, agent access, links, and local/hybrid/shared tracker types, see [Collaborative Trackers](/team-collaboration/trackers.md). Plans and other full-document tracker items start out local to your machine. You can share an individual item with your team so everyone works from the same copy, and edits sync both ways, including changes made offline. ### Share an item Open the item's detail panel and click **Share**. The button switches to **Shared** and the item becomes visible to your team. Click **Shared** again to make it local-only. Sharing is available when: * Your workspace has a team configured, and * The item is a native tracker item or one backed by a markdown file (frontmatter or imported). Inline tracker items, the ones written as markers inside a document, are always local. Promote one to a full item first if you want to share it. Some tracker types are shared with the whole team by design; those are always shared and have no per-item toggle. ### What stays in sync Once an item is shared, its status, lifecycle, and body stay in sync across the team. Edits from teammates flow back to you, and edits you make offline sync the next time you reconnect. Session links are personal, so they are cleared when an item becomes shared. ### Seeing what is shared Each item carries a small sync indicator: local, pending (waiting to sync), or synced. To scan sharing across many items at once, turn on the optional **Shared** column in the table view (see [Views: Kanban, List, and Tag Board](/task-management/kanban-and-list.md)). It is off by default. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nimbalyst.com/task-management/sharing-plans-and-trackers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.