Skip to main content

​
Manage Users

Follow the instructions in the video for how to add users to your organization.
All user types can use the Chat and run existing playbooks against contracts.There are additional permissions that are specific to the 3 available user roles:
  • Contract Owner - the default user role. Contract owners can use the Chat and review contracts using existing playbooks. In the Web App, they will only be able to see their own contracts.
  • Playbook Admin - Playbook admins can create and edit playbooks in the Chat or the Web App. For smaller teams where fewer controls are needed around approved playbooks, we recommend making every team member a Playbook Admin.
  • Organization Owner - can see all playbook-reviewed contracts and can invite and remove users from the organization.

​
Create Automated Workflows

​
Integrations

Dioptra can connect with your existing systems to send and receive contracts and contract data and can be enabled to access the internet directly. If you require assistance with configuring an integration, please reach out to a member of the Dioptra team directly. Integration options include:
ICI Instructions
  1. [administrator step] Add the four URLs listed below to the “AllowedRedirectURIs” Config Key in the applicable ICI instance. Each URL should be added separately and in addition to any pre-existing URLs.  
Picture A
  1. Save update and push for approval / publishing.
  2. The approver approves and clicks on “Push Changes to Icertis Platform”.
  3. Once published, proceed to Vera Engage Steps.
Configure Vera Engage <> ICI Integration
  1. [administrator step] Navigate to the Vera Engage web-app and login with your credentials. The url for the organization you have just created depends on the project and environment it was set up in — the table below includes the applicable urls.
  2. [administrator step] Click on the profile initials in the upper righthand corner of the screen and select “Integrations”.
    Picture B
  3. [administrator step] From the integrations page, select “Icertis” and then add the base url of the applicable Icertis platform instance (ICI). This will define the ICI backend for users.
    Picture C
  4. [user step] Open the Vera Engage Word add-in and click “Icertis” on the login page. Then select the appropriate region and environment based on geographic location and stage of instance (staging/UAT vs production). If you are unsure which region or environment to select, contact a member of the Vera Engage team for assistance. Once the appropriate backend is selected, click “Login” and follow the instructions to log in to your account.
    Screenshot2026 03 30223630
  5. [user step] The first time a user has opened the Vera Engage Word add-in a document that has come from ICI, a new “Icertis” section will appear at the top of the admin panel with a button that says “Reconnect & Upload”. To perform the authentication the user needs to click “Reconnect & Upload”. A pop-up will flash on the screen and once the authentication is complete the “Reconnect & Upload” button will be replaced with a button that says “Upload to workflow”. Selecting “Upload to workflow” will now upload the open document back to ICI as a new version.
    Screenshot2026 03 30223744
  • Sharepoint
  • Web search

​
SSO

Dioptra can connect with your organization’s existing SSO provider to provide a seamless sign-in experience.
NOTES
  • This process will need to be completed by a customer SSO admin who has access to customer’s Identity Provider (IDP) and a Vera Engage (Dioptra) admin account.
  • Customers will need to separately set up SSO for Staging (UAT) and Production environments of Vera Engage (Dioptra), if applicable.
  • SSO setup for ICI will not work with Vera Engage (Dioptra). Customers will need to separately set up SSO for both ICI and Vera Engage (Dioptra).
SSO SETUP INSTRUCTIONS
  1. [administrator step] Navigate to the Vera Engage (Dioptra) web-app and login with your credentials. The applicable url for your organization will depend on the specific project and environment where it was configured. The table below includes the applicable urls.
  2. [administrator step] Click on the profile initials in the upper righthand corner of the screen and select “Profile”.
    Picture1 1
  3. [administrator step] From the Profile page, select “Settings” under “Organization” and then select “Enable Enterprise SSO”.
    Picture2 1
  4. [administrator step] Select your applicable Identity Provider (IDP) from the list, select SAML or OIDC, then follow the step-by-step instructions to set up SSO with your particular IDP. The steps are different for each IDP and are set-forth within the web-app.
    Picture3
  5. Additional documentation from PropelAuth is available here: https://docs.propelauth.com/overview/misc/saml-setup-guide-example.