As the project-owning organization, you can prevent an organization from editing or creating project data by restricting it to read-only or archive access.
There are two levels of restricted access:
Changing an organization’s access level does not prevent users from seeing their own data or anything which has already been sent to them. It does restrict the types of actions users will be able to perform, from that point onwards.
When should Read-only access be used?
Use Read-only access for projects that only store project reference materials, such as OH&S (Occupational Health & Safety) documentation.
What do organizations with Read-only access have access to?
They can receive and read project mail and updated documents.
What restrictions apply to organizations with Read-only access?
Module | Organizations with Read-only access cannot |
---|---|
Documents | Upload, supersede, transmit, auto-update, mark as No Longer in Use, restore as current, perform bulk processing |
Create new mail, register mail, reply / reply all, forward, approve, reject | |
Workflows | Create templates, initiate a workflow, be a workflow administrator, review a workflow step |
How does an organization know it has restricted access to the project?
Users in organizations with Read-only access will see Read-only next to the project name.
When should Archive access be used?
Use Archive access for organizations that no longer have active involvement with your project.
What do organizations with archive access have access to?
Setting an organization to archive access effectively removes them from participation on the project.
How does an organization know it has restricted access to the project?
Users in organizations with Archive access will see Archive next to the project name.
Follow the instructions here: Switch an organization to read-only or archive access