Collaborative documents your team can write, review, and find — together

The document editor supports a full block-based rich-text model: heading levels, paragraph text, bullet and numbered lists, to-do checkboxes, blockquotes, code blocks with syntax highlighting for common languages, horizontal dividers, and inline images. A slash-command menu (type / anywhere in a document) surfaces all block types without leaving the keyboard, keeping writing flow uninterrupted. Documents auto-save to the server every few seconds, with local recovery if the browser closes unexpectedly.

Multiple team members can open and edit the same document simultaneously. Each collaborator’s cursor is shown in a distinct colour with their name label, and changes appear on all screens within milliseconds using an operational-transform engine that resolves conflicting edits automatically. A presence bar at the top of the document shows who is currently viewing or editing, so authors can coordinate in a sidebar chat thread if needed.

By default a document is private to its creator. Sharing opens a panel where the author grants specific users or teams view-only, comment-only, or full edit access. A public link option generates a read-only URL that can be shared externally without requiring a Hitaji360 login. Permission changes take effect immediately and are logged in the document’s activity feed, giving a clear audit trail of who was granted access and when.

Every meaningful save (auto-save or manual) creates a timestamped version snapshot. The version history panel shows a scrollable timeline of snapshots, each with the editor’s name, timestamp, and a diff view highlighting what changed. Clicking "Restore this version" replaces the current document with the selected snapshot while recording the rollback as a new version entry, preserving the full history rather than truncating it.

Select any range of text and click the comment icon to open a comment thread anchored to that passage. Comment threads support replies, @mentions, and emoji reactions. Open comments are visible as highlighted passages in the document body; resolved comments are archived but searchable. Authors can resolve, re-open, or delete comment threads, and all activity feeds into the document’s notification stream so collaborators stay informed without having to poll the document manually.

Documents are organised in a nested folder hierarchy inside Spaces — named top-level containers that map naturally to teams, departments, or subject areas (e.g. "Engineering Specs", "HR Policies", "Client Deliverables"). Folders and documents can be moved, renamed, or duplicated. A global document search spans all spaces the user has access to, returning results ranked by recency and relevance with a text snippet showing the matched passage.

Any document can be linked to a project in the Project Management module. Linked documents appear in a "Docs" tab on the project page alongside tasks and milestones, making specs, meeting notes, and decision records immediately findable by anyone on the project without knowing which Space they live in. Conversely, the document header shows which projects reference it, giving authors visibility into where their writing is being used.