Privacy and safe sharing
dtxWiki keeps knowledge on the computer or server where you install it. “Local first” describes where the application stores data; you still choose how to share pages and whether to connect external services.
Decide who should see the material
Use a private workspace for work that should be limited to its members. Membership covers the whole workspace rather than one folder. A private edit in progress is author-only until it is submitted; the later review and published states have their own access rules.
There are three distinct sharing decisions:
| Action | Who gains access? |
|---|---|
| Add a member | That account receives the selected role across the workspace |
| Copy a workspace page link | Only a signed-in member with the required access can open it |
| Publish a Context version to the web | Anonymous visitors can read the separately published version |
An unlisted public URL still allows anyone who obtains the URL to read it. Treat it as external sharing, not a confidential invitation. A Public workspace exposes a discoverable profile; it does not automatically publish all internal pages. Review Sharing before publishing.
Understand AI data access
Connecting an AI app through MCP lets that app request content and permitted actions from the running dtxWiki server. It uses your account, role, chosen workspaces, and scopes. Content returned to the app may then be processed by its AI provider under that provider’s policies. Configure only the workspaces and actions the app needs.
Configuring dtxWiki’s own model provider is a separate choice. Ask works without it. With a provider enabled, the service sends the question and selected evidence to that provider to compose an answer. An external embedding service receives text used for semantic indexing or queries; an external reranker receives candidates to rank. These choices are off by default. See Optional AI providers.
Library ingestion of a web source can contact that source’s host. Optional account mail recovery sends the recipient address and account-link message through the configured mail service; mail is disabled by default. See Optional email delivery for the Gmail example and delivery checks. Local storage does not mean every optional workflow is disconnected from the network.
Protect access keys
An access key, also called a PAT, allows an app to act with the permissions you grant. Treat it like a password.
- Give each person and connection its own key; avoid shared credentials.
- Start with read access if the app only needs to consult knowledge.
- Set an expiration and select only the required workspaces.
- Copy a new key when shown once, then keep it in an approved secrets store.
- Revoke lost or exposed keys in Settings → MCP access and create a replacement.
Do not paste keys, one-time reset URLs, .env files, or full client configurations into public issues, documentation screenshots, or shared chats. Some client configurations store the PAT in plain text, even if the setup helper hides it from terminal output. Restrict those files and their backups.
OAuth avoids manually placing a PAT in a configuration file, but the app still receives tokens and permissions. Read the consent screen and revoke an app you no longer use.
For the operator
Use HTTPS for remote access. Limit exposed ports and trust forwarded headers only from the actual reverse proxy. Keep signing keys and session secrets stable across ordinary restarts, and include them in protected backups.
SQLite files and uploads need operating-system permissions and disk/backup protection. dtxWiki’s application access controls do not replace disk encryption or prevent a server operator with filesystem access from reading stored data. Workspaces are logically separated in a single database in this version.
Do not disable security guards to silence an error. Use Troubleshooting to resolve the configuration or certificate issue. Review Backups and maintenance before key rotation, restore, or a version change.
Version evidence: sharing screen rules, membership and key controls, provider and storage settings.