Collaborative documents & editor media
Create supporting Documents and use private inline images and safe message links.
A supporting Document is a first-class Resource with its own title, icon color, collaborative editor, and stable nested route beneath the owning Initiative, Feature, or Issue.
Create and edit a Document
Choose New document from the Resources row. Integrity creates the Document on the current parent and opens its page. People with edit access can collaborate in real time; readers without edit access receive the same display-safe content in read-only mode.
The Document's route slug is stable. Renaming the title or changing its icon color does not break copied links. Accessible Documents can be opened from workspace search and added to Favorites.
Use the Document menu to:
- rename it or change its icon color;
- duplicate it on the current parent;
- move it to another Initiative, Feature, or Issue of the same family;
- delete it to recoverable state and restore it later.
Moving requires Resource-management permission on both the source and destination. Supporting Documents do not have independent sharing, and they cannot move across object families.
Private inline images
Paste or drop PNG, JPEG, or WebP images into a primary or supporting Document. A local preview appears while Integrity uploads the image. The saved editor content keeps an opaque media identity rather than a public or signed storage URL, and every later image read passes through an authenticated application route.
Image controls support resizing, opening, downloading, copying, copying an authenticated application link, and deletion. Deletion waits for server confirmation before removing the image from the document. Failed uploads or retirement cleanup remain recoverable and surface a friendly error.
Gmail and Outlook message links
Paste a Gmail or Outlook message URL, or use the editor's email-message link command, to create a readable link card. You can edit its text and address or remove it later. Integrity validates the provider URL and opens it safely in a new tab; it does not fetch, store, or preview the email message body.
Markdown links and spreadsheet-table paste keep their normal editor behavior. Creating an email-message link does not create a Resource.
Document body edits and inline-image changes remain Document provenance. They do not send Inbox or email notifications and do not create noisy parent Activity for every edit.