Configure Cloud Applications to Use with API-Based Data Protection

Create the Asana Application for API-Based Data Protection

1. Log in to the Asana application with admin credentials at https://app.asana.com/-/login.
2. Click the drop-down list in the top right corner, and then click Settings.
   
   
    
3. Click Apps in the top menu bar of the settings window, and then click Manage Developer Apps.
    
   
4. Click Create New App in the new window. Enter the name, check the use cases, and agree to the terms and conditions.
    
   
5. Click Create App.

Configure the Asana Application for API-Based Data Protection

1. In the application window at https://app.asana.com/0/my-apps/<app-client-id>/settings, select OAuth in the left menu bar, and then configure the callback URL in the Redirect URLs field.
   
   
    
2. Select Manage Distribution, and then click Any Workspace.
   
   

Configure Asana Webhooks Manually

Webhooks are automatically established and managed, but you can manage them manually.

To configure webhooks manually:

1. Obtain the resource ID of interest by going to https://developers.asana.com/reference/rest-api-reference. Select the desired resource on the right, and then select Get Multiple for the resource (here, workspaces). You need to use a valid access token. 
   
   
    
   Note: It is often necessary to start with parent resources to locate a specific resource identifier. The organizational level is as follows:
   
   Workspace
   • Projects
     • Section
       • Tasks
         • Subtasks
       • Milestones
         • Subtasks 
       • Attachments
   • Users
     • Section
       • Tasks
         • Subtasks
       • Milestones
         • Subtasks 
     • Attachments
       
       If the parent ID is unknown, you can trace backward up the tree to find a resource ID. You need to find the token only for the workspace IDs.
        
2. Using the ID of the resource, establish a webhook on https://developers.asana.com/reference/createwebhook. To do this, enter the resource ID and target URL under “Body params->data” and then click “Try it!”. Larger resources, such as workspaces, may need filtering into their sub-resources; that is, Workspace filtered into its projects.
   
   

Configure an Asana Connector

To configure an Asana connector:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar. 
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Asana in the left column, then click the  Add icon. The Add Instance – Asana screen displays.
   
   
    
4. Specify the Instance name and Admin email, then select the required services.
    

   Field	Description
   Instance Name (Required)	Enter the name of the instance.
   Admin Email (Required)	Enter the email address of the Asana administrator account.
   Retro Scan	Select to scan and protect all the files and objects that are present on Asana at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan.
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services for which this instance will be used. API Based Data protection: Scan and protect content
   Confirm	Select to indicate that the steps mentioned in the previous section to configure the Asana account have been followed.

5. Click Submit. The instance displays in the main pane.
6. In the Access column, click Grant Access to start the OAuth 2.0 process, which grants the application access to the Versa API-DP cloud.
   
   
   
   This opens a login prompt for the Asana account. Use administrator credentials to log in and grant access. Webhooks for existing workspaces will be automatically established during this OAuth process.

Configure Box for API-Based Data Protection

To configure a new instance for Box:

1. Login to Box using administrator credentials, then navigate to the Admin Console.
2. Click Integrations in the left menu bar.
3. Select the Platform Apps Manager tab, and then click Add Platform App.
   
   
    
4. Enter client IDs llr69xaxc0hhgj1tjrjfvfakseo14sj6 and x3v80p6m1do1ynkf3l0wzm9ud90mxftu.
5. Click Next and Authorize. The screen displays entries for Prod-Versanow-Skill and Versa JWT Connector.
   
   
    
6. Select the User Authentication Apps tab, and then click Add Platform App.
7. Enter client ID pb7ww11ovrjotq1oimr930i5ft1jh8po.
8. Click Next and Authorize. An entry for Versa API-DP Box OAuth2 Connector displays.
   
   
    
9. Change the URL from /master/custom-apps/userauth to /master/skills.
10. Click Add Skill.
    
    
     
11. In the Add Custom Skill screen, enter Client ID llr69xaxc0hhgj1tjrjfvfakseo14sj6, and then click Next .
    
    
     
12. Select the content that you want to configure, and then click Next.
    
    
     
13. Select All content in your company, and then click Next.
14. Click Enable to complete the Box configuration.

If you plan to revoke or delete an instance, after you revoke the instance from Concerto, follow the steps below to complete the removal process: 

1. Login to the box using the same admin credentials you used when granting access.
2. Go to the Admin console.
3. Click Apps in the left menu.
4. Select Custom App Manager.
5. Disable the Prod-Versanow-Skill and Versa JWT Connector applications using the More option (“...”) in the application entry.
   
   
    
6. Similarly, under User Authentication Apps, disable Versa API-DP Box OAuth2 Connector.
7. Change the URL to /master/skills.
8. Click Prod-Versanow-Skill.
9. Click Delete. If you are unable to delete, click Disable.
   
   

Configure a Box Connector

To configure a connector for Box in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profiles and Connectors > Saas and IaaS Connectors.
   
   
   
   The following screen displays.
   
   
    
3. Select the SaaS tab, select Box in the left column, then click the  Add icon. The Add Instance — Box window displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Box administrator account.
   Poll Interval (in Minutes) (Required)	Enter the poll interval. Range: 15 through 1440 minutes Default: 60
   Retro Scan (Group of Fields)	Click to scan and protect all the files that are present on Box at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services for which the instance is used. API-Based Data Protection—Scan and protect content. Forensic—Use this instance for forensics. Legal Hold—Use this instance for legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Box account are complete.

5. Click Submit. The new instance is added to the Box application and displays in the Application Connectors > SaaS screen.
   
   
    
6. In the main pane, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud.
   
   A popup window showing the login prompt for the Box account displays.
   
   
    
7. Use the Administrator credentials to login. The next screen shows the permissions that the Versa service requires to scan and monitor the Box account.
8. Click Grant Access to Box to complete the Box connector configuration.

Configure Cisco Webex Teams for API-Based Data Protection

To configure a new instance for Webex:

1. Sign into Webex Developer and Go to https://developer.webex.com/my-apps/new/integration. In the New Integration screen, enter information for the following fields.
   
   
    

   Field	Description
   Integration name	Enter the name of the integration as it will appear in Webex.
   Icon	Upload your own icon or select a Webex default icon.  Icons must be exactly 512x512px in JPEG or PNG format.
   App Hub Descriptor	Enter information about the application, up to 1024 characters.
   Redirect URI(s)	Enter one or more URIs that a user will be redirected to when completing an OAuth grant flow.

2. Click Create Integration. The following screen displays.
   
   
    

3. Store the Client ID and Client Secret for later use.

Configure a Cisco Webex Connector

To configure a Cisco Webex connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Cisco Webex Teams in the left menu bar, and then click the  Add icon. The Add Instance — Cisco Webex Teams window displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Cisco Webex administrator account.
   Organization Name	Enter the name of the Cisco Webex Teams organization.
   Poll Interval (in Minutes) (Required)	Enter the poll interval. Range: 15 through 1440 minutes Default: 60
   Retro Scan	Click to scan and protect all the files that are present on Webex at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content
   Confirm	Click to confirm that the steps required to configure the Cisco Webex account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to the new instance to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens the login prompt for the Cisco Webex Teams account. Use the administrator credentials to log in and grant access.

Configure Citrix ShareFile for API-Based Data Protection

To configure a new instance for Citrix Sharefile.

1. Go to https://api.sharefile.com/apikeys. The Your API Keys screen displays
   
   
    
2. Click Create New. The API Key Generator screen displays.
   
   
    
3. Enter an application name and the redirect URL, then click Generate Api Key.
   
   
    
4. Store the Client ID and Client Secret for later use.

Configure a Citrix ShareFile Connector

To configure a Citrix ShareFile connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select SaaS tab, select Citrix ShareFile in the left menu bar, and then click the  Add icon. The Add Instance — Citrix ShareFile screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Citrix ShareFile administrator account.
   Poll Interval (in Minutes) (Required)	Enter the poll interval. Range: 15 through 1440 minutes Default: 60
   Retro Scan	Click to scan and protect all the files that are present on Citrix ShareFile at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content Forensic—Use this instance for forensics Legal Hold—Use this instance for legal hold Quarantine—Use this instance for quarantine files
   Confirm	Click to confirm that the steps required to configure the Citrix ShareFile account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Citrix ShareFile account. Use the administrator credentials to log in and grant access.

Configure Confluence for API-Based Data Protection

To configure Confluence for API-DP:

1. Go to https://www.atlassian.com/ and select your organization.
   
   
    
2. From the left menu, go to Apps > Sites and choose the site where you want to install the application.
   
   
    
3. In the left menu, select Site Settings > Access requests > Connected apps.
   
   
    
4. In the Connected apps screen, select Settings in the submenu.
   
   
5. Under the Development mode section, click on Enable Development mode, and enable it.
   
   
6. Click Install a private app in the top-right corner.
   
   
7. In the Install private app popup window:
   1. Choose Confluence from the first dropdown menu.
   2. Copy and paste the App Descriptor URL (provided on connector) into the “App descriptor URL” field.
   3. Click Install app to complete the installation.
      
      
       
8. After initiating the installation process, allow some time for the application to be installed and configured. Once completed, the process is finished.
9. If you plan to revoke or delete an instance, after you revoke the instance, perform the following steps to ensure that the instance has been completely removed.
   1. Log in to your Atlassian account.
   2. Remove access from the Atlassian account settings:
      1. Go to Settings > Atlassian Account Settings > Connected Apps.
      2. Locate Versa-APIDP-Confluence, and then click Remove Access.
         
         
          
   3. Uninstall the Versa Networks–Confluence Event Watcher application:
      1. Follow steps 1, 2 and 3 to navigate to the Connected apps section.
      2. Locate Versa Networks–Confluence Event Watcher and click View app details.
         
         
      3. Click the Uninstall button in the top-right corner to uninstall the application.
         
         
          

Configure a Confluence Connector

To configure a Confluence connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Confluence in the left column, then click the  Add icon. The Add Instance — Confluence screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Confluence administrator account.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Site URL (Required)	Enter the URL of the site.
   Retro Scan	Click to scan and protect all the files that are present on Confluence at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content
   App Descriptor URL	Click the  Eye icon to show the app descriptor URL.
   Confirm	Click to confirm that the steps required to configure the Confluence account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Confluence account. Use the administrator credentials to log in and grant access.

Configure Dropbox for API-Based Data Protection

For Dropbox, no configuration is required.

Configure a Dropbox Connector

To configure a Dropbox connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Dropbox in the left column, and then click the  Add icon. The Add Instance — Dropbox screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Dropbox administrator account.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 100 through 1440 minutes Default: 150 minutes
   Retro Scan	Scan and protect all the files that are present on Dropbox at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content. Forensic—Use this instance for Forensics. Legal hold—Use this instance for Legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Dropbox account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. Use Dropbox Administrator credentials to log in and grant access.

Configure Egnyte for API-Based Data Protection

To configure a new instance for Egnyte:

1. Go to https://developers.egnyte.com/member/register, and enter the required information.
   
   
   
   
    
2. Click Register. You will receive an email at the address you entered during registration.
3. Click the link in the email.
4. Sign in at https://developers.egnyte.com/apps/mykeys. The My API Keys screen displays.
   
   
    
5. Store the Key and Secret for later use.

Configure an Egnyte Connector

To configure an Egnyte Connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Egnyte in the left column, then click the  Add icon.The Add Instance — Egnyte screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Egnyte administrator account.
   Domain Name (Required)	Enter the name prefix used in Egnyte domain name.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 150 minutes
   Retro Scan	Scan and protect all the files that are present on Egnyte at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content. Forensic—Use this instance for forensics. Legal hold—Use this instance for Legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Egnyte account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. Use Egnyte Administrator credentials to log in and grant access.

Configure Google Drive for API-Based Data Protection

To configure a new instance for Google Drive:

1. Log in to the Google Drive Admin console using administrator credentials.
   
   
2. Select Security > Access and Data Control > API controls in the left menu bar, and then click Manage Domain-wide Delegation.
   
   
3. In the Domain-wide Delegation screen, click Add New.
   
   
4. In the popup window, enter information for the following fields.
   
   
    

   Field	Description
   Client ID	Add client ID 113866028843424440405.
   Scopes	Add the following scopes. When entering multiple scopes, separate each scope with a comma. https://www.googleapis.com/auth/admin.datatransfer https://www.googleapis.com/auth/admin.directory.customer https://www.googleapis.com/auth/admin.directory.domain.readonly https://www.googleapis.com/auth/admin.directory.group https://www.googleapis.com/auth/admin.directory.group.member https://www.googleapis.com/auth/admin.directory.group.member.readonly https://www.googleapis.com/auth/admin.directory.group.readonly https://www.googleapis.com/auth/admin.directory.user https://www.googleapis.com/auth/admin.directory.user.readonly https://www.googleapis.com/auth/admin.directory.user.security https://www.googleapis.com/auth/admin.reports.audit.readonly https://www.googleapis.com/auth/cloud-platform https://www.googleapis.com/auth/drive https://www.googleapis.com/auth/drive.activity.readonly https://www.googleapis.com/auth/drive.appdata https://www.googleapis.com/auth/drive.file https://www.googleapis.com/auth/drive.metadata https://www.googleapis.com/auth/drive.metadata.readonly https://www.googleapis.com/auth/drive.photos.readonly https://www.googleapis.com/auth/drive.readonly https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile openid

5. Click Authorize.

Configure a Google Drive Connector

To configure a Google Drive connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Google Drive in the left column, then click the  Add icon. The Add Instance — Google Drive screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email	Enter the email address of the Google administrator account.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on Google Drive at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content. Forensic—Use this instance for forensics. Legal Hold—Use this instance for legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Google Drive account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Google account. 
   
   

7. Use Google Drive Administrator credentials to log in. The next screen shows the permissions that the Versa service requires to scan and monitor the Google Drive account. Click Accept to grant access to the Google Drive account.
   
   

Configure Gmail for API-Based Data Protection

To configure a new instance for Gmail:

1. Login to https://admin.google.com as an administrator.
2. Click Security > Access and data control > API controls in the left menu bar.
   
   
3. In the API controls screen, click Manage Domain-wide Delegation, as shown below.
   
   
    
4. In the API Clients Label, click Add New, and then enter information for the following fields.
   
   
    

   Field	Description
   Client ID	Enter the client ID 105557577682135063975.
   OAuth Scopes	Enter the following two OAuth scopes, separated by a comma. https://mail.google.com/ https://www.googleapis.com/auth/admin.directory.user

5. Click Authorize.

Configure a Gmail Connector

To configure a Gmail connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Google Gmail in the left column, then click the  Add icon. The Add Instance — Gmail screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Google administrator account.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 60 through 1440 minutes Default: 120 minutes
   Services	Select the services to use for the instance. API Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Google Gmail account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. Use Google Administrator credentials to log in and grant access.

Configure GitHub for API-Based Data Protection

To configure a new instance for GitHub:

1. Browse to https://github.com/apps/versa-api-dp
2. Click Install.
   
   
    
3. Select the organization on which to install GitHub.
   
   
    
4. Grant permission to all or selected repositories, and then click Install.

If you plan to revoke/delete an instance, once after revoke is done, please follow the steps below to uninstall the Versa–API–DP Notifier app: 

1. Login to your GitHub account.
2. Navigate to the settings of the organization to which you granted access, then go to Third-party Access > GitHub Apps.
3. Locate Versa-API-DP, click on Configure, and then select Uninstall.
   
   

Configure a GitHub Connector

To configure a GitHub connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the Saas tab, select GitHub in the left column, and then click the  Add icon. The Add Instance — GitHub screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the GitHub administrator account.
   Organization Name (Required)	Enter the name of the organization.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on GitHub at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the GitHub account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. Use GitHub Administrator credentials to log in and grant access.

Configure GitLab for API-Based Data Protection

To configure a new instance for GitLab:

1. Login to GitLab as an administrator.
2. Click the Menu icon and select Admin.
   
   
    
3. In the Admin Area left menu bar, select Applications, and then click New Application.
   
   
    
4. In the Add New Application popup window, enter information for the following fields.
   
   
    

   Field	Description
   Name	Enter a name for the application.
   Redirect URI	Enter the redirect URI.
   Trusted	Not applicable.
   Confidential	Select confidential.
   Scopes	Click the checkbox to select all scopes.

5. Click Save application. 
6. Note down the application ID and click the Copy icon to copy the secret value. Save this information to use when you create the GitLab connector.
   
   
    

Configure a GitLab Connector

To configure a GitLab connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select GitLab in the left column, then click  Add. The Add Instance — GitLab screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the GitLab administrator account.
   Client ID (Required)	Enter the client ID.
   Client Secret (Required)	Enter the client secret.
   Domain Name (Required)	Enter the domain name of the GitLab instance. For example, gitlab.companyname.com.
   Poll Interval (in Minutes)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on GitLab at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours), 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Redirect URI	Click the  Show icon to show the redirect URI.
   Confirm	Click to confirm that the steps required to configure the GitLab account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. Use GitLab Administrator credentials to log in and grant access.

Configure Jira for API-Based Data Protection

To configure Jira for API-DP:

1. Go to http://atlassian.com and select your organization.
   
   
    
2. In the left menu bar, go to Apps > Sites and choose the site where you want to install the application.
   
   
    
3. In the left menu, select Site Settings > Access requests > Connected apps.
   
   
    
4. In the Connected apps screen, select Settings in the submenu.
   
   
    
5. Under the Development mode section, click on Enable Development mode, and enable it.
   
   
    
6. Click Install a private app in the top-right corner.
   
   
    
7. In the Install private app popup window:
   1. Choose Jira from the first dropdown menu.
   2. Copy and paste the App Descriptor URL (provided on connector) into the “App descriptor URL” field.
   3. Click Install app to complete the installation.
      
      
       
8. After initiating the installation process, allow some time for the application to be installed and configured. Once completed, the process is finished.
9. If you plan to revoke or delete an instance, after you revoke the instance, perform the following steps to ensure that the instance has been completely removed.
   1. Log in to your Atlassian account.
   2. Remove access from the Atlassian account settings:
      1. Go to Settings > Atlassian Account Settings > Connected Apps.
      2. Locate Versa-APIDP-Jira, and then click Remove Access.
         
         
   3. Uninstall the Versa Networks–Jira Event Watcher application:
      1. Follow steps 1, 2 and 3 to navigate to the Connected apps section.
      2. Locate Versa Networks–Jira Event Watcher and click View app details.
         
         
          
      3. Click the Uninstall button in the top-right corner to uninstall the application.
         
         

Configure a Jira Connector

To configure a Jira connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profiles and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Jira in the left menu bar, then click the Add icon. The Add Instance – Jira window displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Jira administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Site URL (Required)	Enter the URL for the site.
   Retro Scan	Click to scan and protect all the files that are present on Jira at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   App Descriptor URL	Click the  Show icon to display the App Descriptor URL.
   Confirm	Click to confirm that the steps required to configure the Jira account are complete.

5. After adding the instance, click Grant Access to start the OAuth 2.0 process of granting access to the Versa API-DP cloud. This will open a login prompt for the Jira account. Use administrator credentials to log in and grant access.

Configure Microsoft OneDrive for API-Based Data Protection

For Microsoft OneDrive, no configuration is required.

Configure a Microsoft OneDrive Connector

To configure a Microsoft OneDrive connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Microsoft OneDrive in the left menu bar,  then click the  Add icon. The Add Instance — Microsoft OneDrive screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Microsoft OneDrive administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on Microsoft OneDrive at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content. Forensic—Use this instance for Forensics. Legal Hold—Use this instance for legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Microsoft OneDrive account are complete.

5. Click Submit. 
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This will open the login prompt for the Microsoft account.
   
   

7. Use Microsoft OneDrive Administrator credentials to log in. The next screen shows the permissions that the Versa service requires to scan and monitor the OneDrive account. Click Accept to grant access to Microsoft OneDrive account.
   
   

Configure Microsoft Outlook for API-Based Data Protection

For Microsoft Outlook, no configuration is required.

Configure a Microsoft Outlook Connector

To configure a Microsoft Outlook connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar. 
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Microsoft Outlook in the left menu bar, then click the  Add icon. The Add Instance Microsoft Outlook screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Microsoft Outlook administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 60 through 1440 minutes Default: 120 minutes
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Microsoft Outlook account are complete.

5. Click Submit.
6. After the instance is added, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Microsoft account. Use Microsoft Administrator credentials to log in and grant access.

Configure Microsoft SharePoint for API-Based Data Protection

For Microsoft SharePoint, no configuration is required.

Configure a Microsoft SharePoint Connector

To configure a Microsoft SharePoint connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar. 
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Microsoft SharePoint in the left menu bar, then click the  Add icon. The Add Instance — Microsoft Office 365 Sharepoint Sites screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Microsoft SharePoint administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on Microsoft SharePoint at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API Based Data Protection—Scan and protect content. Forensic—Use this instance for forensics. Legal Hold—Use this instance for legal hold. Quarantine—Use this instance for quarantine files.
   Confirm	Click to confirm that the steps required to configure the Microsoft SharePoint account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Microsoft account.
   
   

7. Use Microsoft SharePoint Administrator credentials to log in. The next screen shows the permissions that the Versa service requires to scan and monitor the Microsoft SharePoint account. Click Accept to grant access to Microsoft SharePoint account.
   
   

Configure Microsoft Teams for API-Based Data Protection

For Microsoft Teams, no configuration is required.

Configure a Microsoft Teams Connector

To configure a Microsoft Teams connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar. 
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Microsoft Teams in the left menu bar, then click the  Add icon. The Add Instance — Microsoft Teams screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Microsoft Teams administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 60 through 1440 minutes Default: 120 minutes
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Microsoft Teams account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Microsoft account. Use Microsoft Teams Administrator credentials to log in and grant access.

Configure Microsoft Yammer for API-Based Data Protection

 For Microsoft Yammer, no configuration is required.

Configure Notion for API-Based Data Protection

For Notion, no configuration is required at the Cisco Webex account.

To create a new integration:

1. Select ellipses (three horizontal dots) in the upper right corner of the Add connections > Manage connections screen.
   
   
    
2. Select My connections in the left menu bar, then click Develop or manage integrations.
   
   
    
3. In the Integrations screen, select + New integration, and then give the new integration a name.
   
   
    
4. In the New integration screen, enter the information below.
   
   
    
   1. Set the Type to Public.
   2. Enter the company name.
   3. Connect to one workspace and fill out the necessary information.
   4. In the OAuth & URIs screen, set the redirect URI.
      
      
       
   5. Client ID is under Secrets.
      
      
      
      Note: A newly added page/database will not automatically connect to the integration. It needs to be manually added to integration.
       
5. Click Save.

Configure a Notion Connector

To configure a Notion connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Notion in the left column, then click the  Add icon. The Add Instance — Notion screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Notion administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on Notion at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Notion account are complete.

5. After adding the instance, click Grant Access to start the OAuth 2.0 process of granting access to the Versa API-DP cloud. This opens a login prompt for the Notion account. Use administrator credentials to log in and grant access.

Configure Salesforce for API-Based Data Protection

There are two parts to configure Salesforce for API-DP:

1. Ensure the administrator account used has sufficient privileges.
2. Install the Versa Networks–Event Watcher app to send an alert when any changes are made to the objects.

Configure a Salesforce Connector

To configure a Salesforce connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profiles and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Salesforce in the left column, then click the  Add icon. The Add Instance — Salesforce window displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter an email address of the Salesforce administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files that are present on Salesforce at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Salesforce account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API-DP cloud. This opens a login prompt for the Salesforce account. Use Salesforce Administrator credentials to log in and grant access. 

Configure ServiceNow for API-Based Data Protection

To configure a new instance for ServiceNow:

1. Login to the ServiceNow instance using an administrator account.
2. Select All and search for OAuth. Select Application Registry under System OAuth
   
   
    
3. Select New in the top right corner to create a new OAuth app.
4. Select “New Inbound Integration Experience”.
   
   
    
5. Click on New Integration and select the “OAuth - Authorization code grant” option.
   
   
    
6. Create an OAuth app with the information for the following fields, then click Submit.
   
   
    

   Field	Description
   Details (Group of Fields)
   Name	Enter a name for the OAuth app.
   Client Secret	Enter a strong, random password, or use the one that ServiceNow creates.
   Redirect URL	Copy the Redirect URL value from the connector.
   Advanced Options (Group of Fields)
   Access Token Lifespan	Enter 3600.
   Refresh Token Lifespan	Enter 25920000.

7. Select the newly created app.
   
   
    
8. Click the lock icon near the client secret option. A blue text block displays that contains the client secret. Copy and store the client ID and client secret for use later during the configuration process.
   
   

Configure a ServiceNow Connector

To configure a ServiceNow connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select ServiceNow in the left column, then click the  Add icon. The Add Instance ServiceNow screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the ServiceNow administrator account.
   Client ID (Required)	Client ID of the OAuth app created.
   Client Secret (Required)	Client secret of the OAuth app created.
   Domain Name (Required)	Enter the subdomain portion of the ServiceNow URL. For example, companyname.servicenow.com
   Retro Scan	Click to scan and protect all the files and other objects that are present on ServiceNow at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Redirect URL	Click the Show icon to display the redirect URL.
   Confirm	Click to confirm that the steps required to configure the ServiceNow account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the ServiceNow account. Use ServiceNow Administrator credentials to log in and grant access.

Configure Slack for API-Based Data Protection

For Slack, no configuration is required.

Configure a Slack Connector

To configure a Slack connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Slack in the left column, then click the  Add icon. The Add Instance — Slack screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Slack administrator account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Slack account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Slack account. Use Slack Administrator credentials to log in and grant access.

Configure Trello for API-Based Data Protection

For Trello, no configuration is required.

Configure a Trello Connector 

To configure a Trello connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Trello in the left column, then click the  Add icon. The Add Instance — Trello screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Trello administrator account.
   Poll Interval (in Days) (Required)	Enter the amount of time between polling events. Range: 1 through 5 days Default: 1 day
   Retro Scan	Click to scan and protect all the files and other objects that are present on Trello at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Trello account are complete.

5. Click Submit.
6. After adding the instance, click “Grant Access” to start the OAuth 2.0 process of granting access to the Versa API-DP cloud. This opens a login prompt for the Trello account. Use administrator credentials to log in and grant access.

Configure a Workplace Custom Integration

To configure a Workplace custom integration:

1. Log in with admin credentials at https://www.workplace.com/.  
2. Click Admin Panel in the left menu bar. 
   
   
   
    
3. Click Integrations under the Admin Panel, and then click Create custom integration in the main pane.
4. Specify a name and a description, and then click Create to create the custom integration.
   
   
    
5. In the custom integration you created, access the App ID, Client ID, and access token from Details in the left menu bar.
   
   Note: Custom integrations do not support the OAuth2 flow; as a result, you must use access token shown in this step. This access token does not expire.
   
   

Configure Workplace Custom Integration Webhooks

To configure Workplace custom integration webhooks:

1. In the application window, click Webhooks in the left menu bar.
   
   
2. In the webhooks window, configure individual webhooks by clicking the Edit icon next to the resource name.
   
   
    
3. Specify the same callback URL and access token for all desired webhooks, select the desired sub-resources, and then click Save.
   
   

Configure a Workplace from Meta Connector

To configure a Workplace from Meta connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Workplace from Meta in the left column, then click the  Add icon. The Add Instance Workplace from Meta screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Workplace from Meta administrator account.
   Domain Name	Enter the domain name of your Workplace from Meta community, for example <domain>.workplace.com.
   Retro Scan	Click to scan and protect all the files and other objects that are present on Workplace from Meta at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Workplace from Meta account are complete.

5. Click Submit.
6. After adding the instance, click “Grant Access” to start the OAuth 2.0 process of granting access to the Versa API-DP cloud. This opens a login prompt for the Workplace from Meta account. Use administrator credentials to log in and grant access.

Configure Zendesk for API-Based Data Protection

To configure Zendesk for API-DP:

1. In Zendesk, go to the Admin center.
   
   
    
2. Add the OAuth client by navigating to Admin Center > Zendesk API > OAuth Client > Add OAuth Client.
   
   
    
3. Set the unique identifier and type to be confidential, redirect url and generate the secret.  Set the unique identifier and redirect URLs, then generate the secret.
   
   
    
4. Click Save. The secret now needs to be stored. The unique identifier and the secret are the client-id and client-secret used to grant access.
5. Go to Apps and integrations > Webhooks > Webhooks, then click Create webhook in the upper right corner.
   
   
    
6. Click the Create Webhook button in the upper right corner of the screen. The Create Webhook screen displays.
   
   
7. Select Trigger or Automation. The following screen displays.
   
   
    
8. Under Add Details, enter the following information:
   1. Enter the Endpoint URL.
   2. Select POST as the request method.
   3. Select JSON as the request format.
9. Select Objects and rules > Business rules > Triggers in the left menu bar. In the Triggers screen, click the Add Trigger button in the upper right corner.
   
   
    
10. Add conditions for when an event happens (in this case, a comment is created/updated).
    
    
     
11. Click Add condition.
12. For Actions, choose the webhook you created.
    
    
     
13. Customize the JSON body.
    
    

Configure a Zendesk Connector

To configure a Zendesk connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar.
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
3. Select the SaaS tab, select Zendesk in the left column, and then click the  Add icon. The Add Instance — Zendesk screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Zendesk administrator account.
   Domain Name (Required)	Enter the domain name of your Zendesk account.
   Poll Interval (in Minutes) (Required)	Enter the amount of time between polling events. Range: 15 through 1440 minutes Default: 60 minutes
   Retro Scan	Click to scan and protect all the files and other objects that are present on Zendesk at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API-Based Data Protection—Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Zendesk account are complete.

5. Click Submit.
6. After adding the instance, click Grant Access to start the OAuth 2.0 process of granting access to the Versa API-DP cloud. This opens a login prompt for the Zendesk account. Use administrator credentials to log in and grant access.

Configure Zoom for API-Based Data Protection

For Zoom, no configuration is required.

Configure a Zoom Connector

To configure a Zoom connector in Versa Concerto:

1. In the Versa Concerto portal, select a tenant under Tenants in the left menu bar. 
2. Go to Configure > Profile and Connectors > SaaS and IaaS Connectors. The following screen displays.
   
   
    
3. Select the SaaS tab, select Zoom in the left column, then click the  Add icon. The Add Instance Zoom screen displays.
   
   
    
4. Enter information for the following fields.
    

   Field	Description
   Instance Name (Required)	Enter a name for the instance.
   Admin Email (Required)	Enter the email address of the Zoom administrator account.
   Retro Scan	Click to scan and protect all the files and transcripts that are present on Zoom at the time of connector creation. Warning: Event-based policies will apply to all the existing data, delete action is irrevocable. Deleted data cannot be restored.
   Start After	Enter the time required to grant access and configure policies and rules for this instance before starting the retroactive scan. Range: 1 through 14 (hours) or 15 through 1440 (minutes) Default: None
   Unit Type	Select the unit of measure for the Start After time, in hours or minutes.
   Services	Select the services to use for the instance. API Based Data protection: Scan and protect content.
   Confirm	Click to confirm that the steps required to configure the Zoom account are complete.

5. Click Submit.
6. After adding the instance, select Grant Access to start the OAuth2 process of granting access to the Versa API data protection cloud. This opens a login prompt for the Zoom account. Use Zoom Administrator credentials to log in and grant access.