Cloud CMS supports locking of nodes (or content instances). Locking allows content editorial team members to explicitly block other editors from working on content that they're already working on.
When a piece of content is locked by a user, all other users in the project who have access to the piece of content will be prohibited from making modifications. They will be able to read the content but they will not be able to save any modifications. Once the lock is released by the user who took out the lock, all others users will once again be able to save changes.
In general, once the lock is taken out, only the user who took out the lock will be able to make changes. Furthermore, only the user who took out the lock will be able to release the lock.
Any users in the project who have Owner or Manager authorities against a locked node will inherit two special capabilities that override the general locking logic:
- They will be able to make changes to the node
- They will be able to unlock the node
This feature is provided so that tenant owners and project managers can correct or adjust for human error or mistakes that occur in the natural progress of working together. There are simply some common scenarios which occur from time to time, such as:
- A team member forgets to unlock a document and then "goes offline"
In this case, the project manager is free to contact the lock owner, confirm they're done and release the lock on behalf of the team member.
- A team member has locked a document and is too tied up working on something else to make a needed change.
In this case, the project manager can step in and make changes. Or they can release the lock and let someone else take the lock out.
- A team member locks the wrong document or is otherwise in a conundrum and needs help.
In this case, the project manager can step in and release the lock for the team member.
There are probably hundreds of interesting variations or irregularities that would introduce the need to have a project manager (or task coordinator) intercede on behalf of the editorial team members. You are free to use this capabilities and the Owner and Manager authorities to set things up as you see fit for your project.