v3.0
Cortex Admin

Configure Client for Vertical and Own Data

Use the following steps to configure a client for a vertical and their own data (for example: setting DPID 4555 - Condor Ferries to access Ground Transportation + own data).

Roles appear below in italics.

  1. Onboarding Staff to search for the customer using the Customers Modal search within the Manage Data Policy view.

    1. If the customer cannot be found, Onboarding Staff to request customer to be created by Engineering.
  2. Onboarding Staff to check for existing policies for this client:

    1. If an existing policy start date is in the past, it cannot be edited, but a new policy can be created, using the past or current policy as a template.

      1. Onboarding Staff to have Support or the Data Partner create a new policy by executing the following steps via the UI:

        1. Login to https://admin.adara.com.

        2. Open the existing policy and Create New Policy, using the past or current policy as a template.

          1. Provide a meaningful Data Policy Name and Description that can be easily found with the Customers Modal search.

            1. Best Practice Define a naming convention for both Policy Name and Description.
          2. Select from the Policy Types available in the drop-down menu.

            1. Select Adara Consortium for Data Partners.
            2. Select Client Use for data intended for use by client only.
          3. Select the desired Boolean operator and itemize the permissions or restrictions desired across any combination of Use Case, Consortium, Vertical, Customer, Account, and/or Platform.

            1. Assign Use Case permission if appropriate.

              1. Setup either Allowed or Restricted.
            2. Assign Consortium permission if appropriate.

              1. Set Adara Consortium to Allowed.
            3. Assign Vertical permission if appropriate.

              1. This is applicable to Data Partners.
              2. Setup either Allowed, Restricted, or both.
              3. Ensure you setup either Allowed or Restricted for “Marketplace”.
            4. Assign Customer permission if appropriate.

              1. Ensure the Client is setup as Allowed so that they can access their own data.
            5. Assign Platform permission if appropriate.

    2. If an existing policy start date is in the future.

      1. Onboarding Staff to have Support or the Data Partner execute the following steps via the UI:

        1. Login https://admin.adara.com.

        2. Open the existing policy and Edit a Policy Version.

          1. Update the Data Policy Name and Description meaningfully so that it can be easily found with the Customers Modal search.

            1. Best Practice Define a naming convention for both Policy Name and Description.
          2. Select from the Policy Types available in the drop-down menu.

            1. Select Client Use for data intended for use by client only.
          3. Select the desired Boolean operator and itemize the permissions or restrictions desired across permissions levels:

            1. Assign Use Case permission if appropriate.

              1. Setup either Allowed or Restricted.
            2. Assign Customer permission if appropriate.

              1. Ensure the Client is setup as Allowed so that they can access their own data.
            3. Assign Platform permission if appropriate.

Consider each specific operation in context to its own situational requirements. This section suggests general workflow and best practices, but consider the unique requirements for the client, their context, and their data when assigning permissions.`