| Table of Contents | ||
|---|---|---|
|
...
The purpose is so that only permitted users can create, view and edit specified files and that the private and confidential files are hidden from public view.
Access is controlled by the SDP content team via permissions.
Permissions
Secure files can only be accessed by people with the Secure files user role. CMS users with this role can add, view, edit, delete and revert secure media files.
Secure file files user permission can be requested via a support request to add or change user permissions. All requests for this permission role must be approved by Paul Bowerman, DTF digital manager.
...
If a website user visits a public web page with a secure file on it (whether embedded or linked), clicking on the file will result in a 404 not found page.
Is this correct?
Editors can embed a file on a page even if they don’t have permission. Why would they want to do that when barely anyone can read the file?