Document Ownership And Access Control
Clarus uses a single-owner document model to keep your writing private and secure.
How It Works
Every document in Clarus belongs to exactly one user — the person who created it. All access to a document flows through this ownership check:
- Only the owner can read or edit a document by default
- Sharing is explicit — you choose who gets access and at what level
- Revoking access is immediate — removed collaborators lose access right away, and the document's encryption key is rotated
Authentication
Clarus supports sign-in via GitHub, Google, and email link. Your identity is verified on every request to ensure only you can access your documents.
What Is Protected
Every layer of your document is access-controlled:
| Layer | Protection |
|---|---|
| Document metadata | Owner-only by default |
| Document body (live editing) | Authenticated ownership check on every sync |
| Version history | Owner verification before any read or restore |
| Annotations and AI feedback | Scoped to the parent document's owner |
| Comments and discussions | Scoped to the parent document's owner |
Sharing
When you share a document with someone:
- They receive their own encryption key for that document
- Their access level (viewer, commenter, editor) determines what they can do
- You can revoke their access at any time
When access is revoked, the document is re-encrypted with a new key that the removed user does not have.