Docly Developers
Knowledge base By design By design

Installed packages are read-only

In shortA package installed from an address is unpacked under # in the workspace root, in a folder named after the package address. Docly replaces that whole folder each time the package is updated, so nobody can change the files in it - not even the workspace owner. Every write made as a user is refused there: the editor, uploads, the docly CLI, MCP and the AI assistant. Only installing, updating and removing the package write in it. To change what a package does, change the package itself and cut a new release; keep your own files in your own folders.
Applies to PackagesWorkspacesdocly CLI
  1. What you'll see

    You try to save, upload, rename or delete a file under #/<package address>/ in a workspace, and Docly answers that you do not have access - even though you own the workspace. Or docly put / docly push is refused for a path inside an installed package.

  2. What's actually happening

    When a package is installed from an address (for example https://packages.docly.net/FileStorage/), Docly unpacks the release under #/ in the workspace root, in a folder named after the address. The package's schemas, templates and code are read from there.

    An update replaces the whole folder. Docly unpacks the new release next to the old one, swaps them, and moves the old folder to the recycle bin. Anything changed inside the package folder would be gone after the next update without warning. That is why the folder is read-only:

    WhatInside an installed package
    Open, read, browse, downloadAllowed
    Save, upload, create, rename, move, delete, share, publishRefused - for everyone, including the owner and admins
    Install, update and remove the package (the Packages tab)The only writes allowed

    The rule sits in Docly's access check, so it is the same for the editor, uploads, the docly CLI, MCP and the AI assistant. Site scripts cannot write under #/ at all.

    Only folders named after an http:// or https:// address are locked. The rest of #/ - your site's own code, services and data - is not affected, and neither are packages added from the catalogue, since those copy no files.

  3. What to do

    Change the package, not the copy

    If you maintain the package, make the change in the package's own workspace and cut a new release (see Publishing a package). Workspaces that have it installed get a notice and an Update button in the Packages tab.

    Keep your own files outside the package folder

    Put customisations, extra templates and your own code in the workspace's own folders, not in #/<package address>/. Then an update never touches them.

    Lost a change made before an update?

    An update moves the previous package folder to the recycle bin rather than deleting it, so an earlier edit can still be found there and copied into one of your own folders.

Last reviewed 19 Nov 2026