Managing User Access

You must have the Application Administrator role assigned to your LiveCycle ES2 user account in order to develop applications. In this role, you can assign limited access to the application development environment for users who have other roles assigned. You can permit other users to have the following type of access:

  • Read:  The user can view the application.
  • Delegate:  Although the user is not the Application Administrator, that user can extend read/write permissions to another user.
  • Write:  The user can modify the application and save the changes.

Essentially one can classify user permissions under the following two categories:

  1. Role Based Permissions
  2. Resource Level Permissions

Role Based Permissions typically would cover the roles that the user has been assigned via the Role Assignment interface and this supersedes the “Resource Level Permission ” which are assigned via the Manage Access interface as described in the following link.

In order to achieve the above scenario one would need to ensure that the user has not been assigned any such permissions which would otherwise allow the user to perform the Read/Delegate/Write operations on an application.

A sample use case of how the above functionality can be achieved effectively is as described below:

  1. Create a custom role say “testRole” with the following permissions; this ensures that the user has basic login permissions in workbench.
    1. Component Read
    2. Service Invoke
    3. Service Read
  2. Assign this role to a test User say “A”.
  3. Assign additional permissions to user A via the “Manage Access” interface in Workbench to  work on an application.
  4. Login to Workbench with with this new user A.
  5. This user only has permissions to work on Applications to which he/she has been granted additional privileges.


This entry was posted in Adobe LiveCycle ES2 (9.0.x). Bookmark the permalink.

Comments are closed.