/
Documentation

Troubleshooting

Issues you may encounter with the Meldoc web app. For CLI-specific issues, see Troubleshooting. For MCP issues, see Troubleshooting.

Document Not Visible

If a document isn’t appearing where you expect, five settings control its visibility. Check them in this order:

  1. Workflow state — A draft document is visible to workspace members only, never to public readers. Publish it to make it available to others.
  2. Document access level — Set under Share → Access → Access Level. Options are Inherit from project, Workspace members, Anyone with the link, and Public.
  3. Project access level — If the document is set to inherit from the project, it follows the project’s access level. A private project keeps all inherited documents members-only.
  4. Navigation visibility — Hidden documents are still accessible by URL but don’t appear in the sidebar.
  5. Password protection — A document set to Anyone with the link, with a password set on the Access tab, can be opened by direct link even when its project is private.

See Document Visibility & Access Level for full details on how these settings interact.

Visibility vs Access Level

These are two independent settings that work together.

Visibility is the Show in navigation toggle on the Access tab — turn it off to keep a document out of the sidebar. Access level controls who can open the document — Inherit from project, Workspace members, Anyone with the link, or Public.

A common misconception: “hidden” does not mean “restricted.” A hidden document with Public access is still reachable by everyone — it just won’t show in the sidebar.

Publishing Safely

Before making a project public, review these steps:

  1. Search all documents for sensitive content (API keys, internal URLs, PII).
  2. Verify workflow states — sensitive documents should stay as Draft.
  3. Set internal documents to the Workspace members access level.
  4. Test the public URL in an incognito browser window.
  5. Confirm the sidebar shows only intended documents.

Tip: To roll back quickly, set Default Access Level back to Private in Project Settings → Access Settings.

Asset Issues

Broken Image

The referenced asset was deleted or moved. Re-upload the file and update the image reference in your document.

Upload Fails

Storage limit reached — delete unused assets or upgrade your plan. File type not supported — convert to a supported format. File too large — compress before uploading.

Orphaned Assets

Assets live at the workspace level. Deleting a document does not delete its assets.

  1. Open the workspace Overview and select the Assets tab.
  2. Select any asset and check Used in Documents.
  3. If empty, the asset is orphaned and safe to delete.

See Managing Assets for full asset management.

Search Not Finding Results

Check spelling, try broader terms, and make sure the document is published. If you’re filtering by project, try selecting All Projects instead.

For Ask AI issues, check your plan limits in Settings → Plan & Billing. See Search & Ask AI for details on how search and Ask AI work.

Getting More Help

Troubleshooting — CLI-specific errors, PATH issues, and cache resets.

Troubleshooting — MCP connection, authentication, and workspace issues.

Contact support at [email protected] or open an issue on GitHub.