LSR User Mapping

Modified on Sun, 8 Jun at 11:33 PM

LSR User Mapping Documentation


LSR User Mapping LSR User Mapping connects approvers to specific offices, determining which requests they can see and manage. This mapping ensures that Legal Service Request (LSR) approvers only have access to requests from offices they are authorized to handle, providing proper access control and workflow management across the platform.


Accessing LSR User Mapping

  1. Navigate to the Settings section by clicking the settings icon in the header bar on the left side.
  2. Under the LSR section, click on LSR User Mapping


Navigating to LSR User Mapping in Settings


Managing Existing Mappings The LSR User Mapping page displays all mappings in a table with:

  • Username
  • Office (comma-separated list)
  • Status
  • Action buttons (Edit and Delete)

You can:

  • Add new user mappings by clicking the Plus (+) button in the top right corner
  • Search across all columns to find specific mappings
  • Edit a mapping by clicking the edit button in the action column
  • Delete a mapping by clicking the delete button in the action column


Existing User Mappings



Adding New User Mapping

  1. On the LSR User Mapping page, click the Plus (+) button in the top right corner
  2. In the popup form, enter:
    • User: Select an LSR Approver from the dropdown using single selection
    • Office: Select one or more offices from the dropdown using multi selection
    • Active: Toggle button set to "Active" (default) or "Inactive"
  3. Click Submit to create the mapping


 

Adding LSR User Mapping to connect approvers with offices


Note: Only users with the "LSR Approver" checkbox enabled in their profile will appear in the User dropdown. To make a user an LSR Approver, edit the user profile in user settings page and enable the "LSR Approver" checkbox.


Reference:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article