> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/the-portal/my-space.md).
# My Space and Sharing
My Space is where your work lives between sessions. Anything you build in the workbench can be saved there, organised, reopened, and shared.
## Saving content
Until it is saved, a workbench tab is working state. Saving it to My Space makes it a piece of content that can be organised, linked to, and shared.
A saved item stores what it points at, not a copy of the data. Reopening it re-reads the records, so a table saved in March shows the records as they are today. Deleting content never deletes the records behind it.
## Finding your way around
The My Space controls
Above the tree are a search box and four shortcuts: **new folder**, **recent**, **favourites**, and **trash**.
The **scope** filter narrows the tree by where content came from:
| Scope | Shows |
| ------------ | ------------------------------------------------ |
| **All** | Everything you can reach |
| **Personal** | Content you own and have not shared |
| **Shared** | Content shared with you, or that you have shared |
| **Global** | Content published to everyone |
Items in the tree carry a marker when they are shared, and a star when you have favourited them.
## Organising
Content is arranged in folders, nested as deeply as makes sense. From an item's menu you can:
* **Rename** it
* **Duplicate** it, producing an independent copy
* **Move** it, by dragging it into another folder
* **Delete** it
**Shortcuts** let one piece of content appear in more than one place without being copied. The shortcut points at the original, so the original stays the single copy that everyone edits.
## Sharing
Content is shared by granting access to named **users** or **groups**, as one of two roles:
| Role | What it allows |
| ---------- | ------------------------------------------------------- |
| **Viewer** | Open the content and see it against live data |
| **Editor** | Change it, and share it with others as viewer or editor |
Grants on a folder apply to everything beneath it, so sharing a folder shares its whole subtree. Where someone holds more than one grant on the same item, the strongest applies.
**Publishing to everyone is separate, and deliberately narrower.** It is view-only and administrator-published. An editor cannot make their own work organisation-wide.
Sharing is enforced on the server, on every read, against the roles and grants in force at that moment. It is not decided in the browser and not stamped onto the content when it was shared, so revoking access takes effect immediately.
## Links
Every page has a link you can copy, from the item menu or the tab strip.
A link is an address, not a key. Sending it grants nothing. The person opening it sees the content only if their roles and grants already allow it. This means a link is safe to paste into a ticket or a chat: it will not leak the content to someone who was not already permitted to see it.
Opening a link restores that page. The rest of your open tabs are restored from your own settings, so a shared link puts the recipient on the page you meant, not into your workspace.
## Deleting and recovering
Deleting behaves differently depending on whose content it is.
**Content you own.** Deleting removes it from My Space and closes its open tab. If you had shared it, it is removed for everyone. Folders and their contents go to a recoverable **Trash**, which can be undone immediately after the fact.
**Content shared with you.** The action is **Remove from my view**. It takes the item out of your space and closes its tab. The original stays available to its owner and to everyone else it was shared with. You cannot delete somebody else's content by tidying your own space.
**Trash.** Deleted items are held with the date they were deleted and can be restored. Each item shows when permanent deletion becomes available. Permanent deletion removes the whole subtree and its Command metadata, and cannot be undone.
## Related
* [The Portal](/command/the-portal/portal.md)
* [Content Types](/command/the-portal/content-types.md)
* [Access Rights](/command/prior-v26.0/configuration/access-rights.md)
---
# 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.ins-pi.com/command/the-portal/my-space.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.