|
The following illustration and list shows various users
interacting with policy-protected PDF documents and Rights Management.
(If Rights Management protects other file types, such as a DOC file,
users can interact with these file types in the same manner.)
Here is an example of how Rights Management works:
The document owner or administrator creates policies
by using the Rights Management web application accessible through
Administration Console. Document owners can create user policies
accessible only to them. Administrators can create organizational
policies within policy sets that are accessible to permitted users,
and can also designate policy set coordinators. The policies are
stored in a database that connects to the application server.
Developers
can also automate the creation of policies by using the Process Design
perspective in Workbench or the Rights Management API.
The document owner applies the policy, and saves and distributes
the document by using the web pages or Adobe Acrobat 7.0 or later.
The document can be distributed by email, through a network folder,
or on a website.
Developers can also automate the application
of policies to documents. They can also automate the distribution
of these documents to end users by using the Process Design perspective
in Workbench or the Rights Management API.
The document recipient opens the document in Acrobat 7.0
or later or Adobe Reader 7.0 or later. The recipient can use the
document according to its policy.
The document owner, policy set coordinator, or administrator
can track documents and modify access to them by using the web pages.
Developers can also track documents by using the Process Design
perspective in Workbench or the Rights Management API.
|
|
|
