π The open-source, offline-first Notion, Obsidian & Confluence alternative. Advanced Markdown, multi-tenant teams, OIDC/SSO, and local S3 backups. Deploy in one command.
title: Collaboration and permissions description: Share knowledge without losing control over access. navigation: icon: i-lucide-users
Permissions can be applied to every node and their content. Alexandrie distinguishes five levels:
| Level | Allows |
|---|---|
| None | No access to the content. |
| Read | View permitted content. |
| Write | Create and edit permitted content. |
| Admin | Manage the relevant structure and settings. |
| Owner | Retain full control over the scope. |
You can grant access to a team, a workspace, a category, or a document. Permissions are inherited down the tree: if you have read access to a workspace, you can read all its categories and documents.
You can also add more granular permissions to a specific document or category, which overrides the inherited access. This is useful for sensitive content that should not be visible to all team members.
Note that permissions can only grow up the tree: if you have read access to a workspace, you cannot remove access to a category or document inside it. You can only add additional permissions to a specific node, which will override the inherited access.

Public sharing
A public link is useful when you need to share one document with someone without an account. Review what it includes first: treat a public link as content available to everyone who has it. You can revoke a public link at any time. You can also give editing access to a public link.
Invite links
Instead of inviting users one by one, you can create an invite link for a workspace. Anyone with the link can join the workspace and will receive the default permissions you set. You can revoke an invite link at any time.
You can share invite as links or 6-digit codes.
Good practices
- Grant the lowest level required.
- Use workspaces to isolate sensitive projects.
- Revoke invitations and links that are no longer needed.
- Use teams if you want to manage access for a group of people rather than individuals.