Asset Folders and Permissions

The site uses one Statamic asset container. Each organisational section has its own canonical folder and a media_kits subfolder. Editors can read shared assets, but writes are restricted to the folder owned by their section.

Permission Boundary

The application enforces the boundary server-side for every write operation, including uploads, folder creation, moves, renames, and deletes. The national administrator role is the exception. The folder mapping and policy rules live in the application rather than in the browser.

Uploads from an entry’s Assets field are routed to the editor’s own section folder when the editor belongs to exactly one section. This keeps shared blueprints usable across all sites while preventing an editor from writing into another section’s folder.

Browser Behaviour

Statamic calculates the Upload and Create Folder buttons at the container level. As a result, those buttons can remain visible while an editor is viewing a read-only folder. Attempting the write is still rejected by the server-side policies.

This is a known user-interface limitation, not a security boundary. Do not rely on hiding a button in the browser to protect an asset. The application policies remain the source of truth until Statamic exposes folder-level permissions in the asset-browser response.