|
Various types of users work with document security to accomplish
different tasks:
-
The system administrator or other information systems
(IS) person installs and configures document security. This person
may also be responsible for configuring global settings for the
server, web pages, and policies and documents.
These settings
may include, for example, a base document security URL, auditing
and privacy notifications, invited user registration notices, and default
offline lease periods.
-
Document security administrators create policies and policy
sets, and manage policy-protected documents for users as required.
They also create invited user accounts, and monitor system, document,
user, policy, policy set, and custom events. They may also be responsible
for configuring the global server, and web page and policy settings
in conjunction with a system administrator.
Administrators
can assign users the following roles in the User Management area
of administration console. Users who are assigned these roles perform their
tasks in the document security user interface area of administration console.
-
Users within the organization who have valid document security
accounts create their own policies, use policies to protect documents,
track and manage their policy-protected documents, and monitor events
that are related to their documents.
-
Policy set coordinators manage documents, view events, and
manage other policy set coordinators (based on their permissions).
Administrators designate users as policy set coordinators for particular
policy sets.
-
Users who are external to your organization (for example,
a business partner) can use policy-protected documents if they are
in the document security document security directory, if the administrator
creates an account for them, or if they register with document security
through an automated email invitation process. Depending on how
the administrator enables the access settings, the invited users
may also have permission to apply policies to documents, to create,
modify and delete their policies, and to invite other external users
to use their policy-protected documents.
-
Developers use the AEM forms SDK to integrate custom applications
with document security.
|
|
|
