Skip to main content

Who can view, upload, edit and delete documents

Learn how organisation roles, site assignments, and visibility settings control access to documents.

D
Written by Darragh Jones

What you can do in the document store depends on your role in the organisation, which sites you're assigned to, and (sometimes) a document's visibility setting.

By role

  • Admin and auditor — view all sites, create and upload, edit metadata, change version status, mark as reviewed, and delete. Admins can also set Visibility.

  • Member, manager, site manager, area manager — view (within their site access), create, upload and edit. They cannot delete documents.

  • Viewer — view only. No Create document, no upload, no Edit metadata, no delete.

If a button is missing, it's usually because your role doesn't allow that action — not because the feature is broken.

Site assignment

  • Admins and auditors see documents for every site in the organisation.

  • Members, viewers and site managers see organisation-wide documents plus documents for sites they're assigned to.

  • Area managers can typically see across sites in the organisation for viewing and editing where the product allows.

If you can't see a site-specific document you expect, check you're assigned to that site and that the top bar site selector isn't hiding it.

Visibility

Admins can set Visibility in Edit metadata:

  • Everyone — people who can already see the document by role and site still can.

  • Admins only — restricts viewing to admins, even if others would normally see it by site.

Use admins-only for sensitive material that shouldn't appear in the general store.

Create, upload and edit

These share the same permission. If you can create, you can upload and edit (within your site scope). The UI hides Create document, Upload file / Upload new version, Edit metadata, Change status and Mark as reviewed when you don't have edit rights.

Delete

Only admins and auditors see Delete document (and bulk Delete). Members never permanently remove documents; they can archive a version via Change status > Archive when they have edit access.

Related

For how roles work across ASR generally, see Roles and what each one can do in Getting Started (if published for your Help Center).

Did this answer your question?