Use Case for Setting Up Agreement Document Protection
This topic describes the use case for setting up an agreement document protection.
This use case gives one example on how to set up protection level for a document and restrict action levels of a specific user. You might use this functionality differently, depending on your business case.
This use case describes how to set up protection level for a document and restrict action levels of a specific user. For example, the Read Only protection level provides read-only access, while the Insert Comments and Track Changes Only level captures modifications made in the document generated by a specific user.
In this case, a System Administrator can specify that a user with the Sales profile is allowed full document access when generating or re-generating a document, but Track Changes is enabled when the user sends a document for review.
Setting Up Agreement Document Protection
Prerequisites:
System Administrator must apply the appropriate settings before enabling the Agreement Protection; protection should be turned on and an unlock password must be created.
To set up protection or restrict access to your document, please perform the following steps:
You have enabled Track Changes for the generated Word document, which cannot be disabled by a user who will edit the agreement document unless the user enters the Unlock password which is set by the Administrator.
