3Mandatory Setup Tasks

This chapter contains the following:

Overview of Mandatory Setup Tasks

This topic describes the mandatory tasks that you must complete to set up Digital Customer Service.

The following list outlines the mandatory tasks that are covered sequentially in this chapter. You can use these steps, like a checklist, to get your Digital Customer Service application set up:

  1. Set Up Oracle Engagement Cloud

    1. Enable Digital Customer Service

    2. Manage User Categories

    3. Set Up the APPID User

    4. Set Up Administrators and Developers

  2. Set Up Oracle Identity Cloud Service

    1. Enable and Perform a User Synchronization

    2. Create a Non-Federated User Account for Developers

    3. Add User Roles

  3. Set Up Oracle Visual Builder

    1. Configure Oracle Visual Builder with Oracle Engagement Cloud

    2. Configure Oracle Visual Builder with Oracle Component Exchange

    3. Create a New Digital Customer Service Application

    4. Add Mappings to User Roles

    5. Set Up Authentication for Your Application

    6. (Optional) Configure Git

Set Up Oracle Engagement Cloud

Enable Digital Customer Service

This topic describes how to enable the Digital Customer Service application in Oracle Engagement Cloud.

You must enable Digital Customer Service in Oracle Engagement Cloud to have access to the following profile options and work areas. Once enabled, the following work areas are grouped with the Service icon in Oracle Engagement Cloud:

  • Self-Service Users

  • Registration Requests

Once enabled, the profile options are available in the following work areas:

  • Manage Digital Customer Service Account Setup Profile Options

  • Manage Digital Customer Service Registration Profile Options

To enable the Digital Customer Service Application:

  1. Sign in to Oracle Engagement Cloud as an administrator or a setup user.

  2. In the Setup and Maintenance work area select the Service offering.

  3. Click the Change Feature Opt In link.

    The Opt In: Service page is displayed.

  4. In the Digital Customer Service row, select the Enable option.

  5. Click Done.

    Digital Customer Service appears in the Functional Areas list. Selecting Digital Customer Service will reveal a related list of tasks.

Manage User Categories

This topic describes how to create user categories, assign categories to users, and modify the email text that is sent to users to reset their passwords.

Create a User Category

This topic describes how to create a user category. User categories are helpful in the context of Oracle Digital Customer Service users. When users are categorized, you can configure the password reset email that is sent to that specific category of users.

To create a user category:

  1. Sign in to Oracle Engagement Cloud as administrator or a setup user.

  2. Navigate to the Security Console.

  3. Click User Categories.

    The User Categories screen appears.

  4. Click Create.

    The User Category: Details screen appears.

  5. Click Edit.

  6. Specify the following details:

    • User Category Name. Specify the name of your user category, for example: ODCS Users.

    • User Category Description. Enter a description for your user category.

    • Next URL. Specify the URL that you want users to be redirected to after a password reset. For Oracle Digital Customer Service, this should be the URL for your published live Digital Customer Service Application.

  7. Click Save and Close.

Modify the Default Category for Users

If you want your users to be automatically assigned to the category that you created in the previous Create a User Category task, you must modify a profile option.

To modify the default category for users:

  1. Sign in to Oracle Engagement Cloud as administrator or a setup user.

  2. In the Setup and Maintenance work area, go to the following:

    • Offering: Service

    • Functional Area: Digital Customer Service

    • Task: Manage Digital Customer Service Registration Profile Options

  3. Click the SVC_CSS_USER_CATEGORY profile option.

  4. Set the Profile Value field to the name of the category that you created in the Creating a User Category task.

  5. Click Save and Close.

Edit the Email Template for Password Reset

After a self-service registration request is approved by the administrator, the user account is created, and an email is sent to the user with instructions on how to reset their password, including a link. The password reset auto-generated email will look similar to the following:

Dear Jane Smith,

A new password has been issued to access your Oracle Fusion Applications.

If you click the following link, you will be able to reset your password.

https://computer.mycompanydomain.com:443/hcmUI/faces/ResetPassword?ase.gid=8018e837f39340a795fbe66b0a609fcd&nextURL=https://computer.mycompanydomain.com:443/release/DCS_AUTO_LIVE/live

If you have any questions, contact your system administrator.
 
Thank You,
Oracle Fusion Applications

Note: Clicking on the link of the email redirects the user to a page where they can reset their password.

The email text is based on the template that is defined by user category. You can modify the text in the password reset auto-generated email.

To modify the text in the password reset auto-generated email:

  1. Sign in to Oracle Engagement Cloud as administrator or a setup user.

  2. Navigate to the Security Console.

  3. Click User Categories.

    The User Categories screen appears.

  4. Click the name of the user category for which you want to edit the email text.

  5. Click Notifications.

    The User Category: Notifications screen appears.

  6. Click the Edit button.

  7. Click Add Template.

    The Add Notification Template dialog box appears.

  8. Specify the following details in the Add Notification Template dialog box:

    • Template Name. Specify a name of your template.

    • Enabled. Select this option.

    • Description. (Optional) Describe the template.

    • Event. Select Password reset from the list.

      In the Notification section, the Message Subject and Message fields are populated with the default text.

    • Edit the text in the Message Subject and Message fields.

    • Click Save and Close.

  9. Click Save.

  10. Click Done.

Assign User Categories to Existing Users

In cases where existing users must reset their passwords, but were assigned to the DEFAULT category rather than the one created in the Modify Default Category task in this topic, the user is redirected to Oracle Engagement Cloud rather than their Digital Customer Service application after performing the password reset. You can fix this issue by modifying the user category of the user, and then send them the password reset email. With the new category assigned, they will be redirected to Digital Customer Service after resetting their password.

To assign an existing user to a category, and send the password reset email:

  1. Sign in to Oracle Engagement Cloud as administrator or a setup user.

  2. Navigate to the Security Console.

  3. Click Users.

    The User Accounts screen appears.

  4. Search for the user.

  5. Click the name of the user for which you want to modify the user category text.

  6. Click Edit.

    The Edit User Account screen appears.

  7. In the User Category list, select user category that you created in the Create a User Category task.

  8. Click Save and Close.

  9. Click Done.

    The User Accounts screen appears, with the search results that you entered in step 4.

  10. Locate the row of the user whose user category that you modified, and select Reset Password from the menu in the Action column.

    The password reset auto-generated email is sent to the user.

Set Up the APPID User

This topic describes how to set up the APPID user for Digital Customer Service in Oracle Engagement Cloud.

Create the Role for the APPID User

An administrator-defined job role with the required privileges for Digital Customer Service must be created and then granted to a new APPID user. The APPID user is required for Sales, Service and self-registration. This task ensures that the APPID user does not have more privileges than required. The APPID user is required in situations where anonymous users need to access services from Oracle Engagement Cloud, such as REST APIs that are restricted.

Once you complete this task, you must complete the subsequent Create the APPID User task to create the APPID user and assign the newly created role to that user.

To create the role for the APPID user:

  1. Sign in to Oracle Engagement Cloud.

  2. Navigate to the Security Console work area and click the Roles tab.

  3. Click Create Role.

  4. In the Role Name field, enter the following text:

    Self-Service APPID Users

  5. In the Role Code field, enter the following text:

    SELF_SVC_APPID_USERS

  6. From Role Category list, select CRM - Job Roles.

  7. Click the Next .

  8. Click the Privileges tab.

  9. Click Add Function Security Policy.

    The Add Function Security Policy dialog appears.

  10. In the Search field, enter each of the following security policies, then click Add Privilege to Role:

    • Create Service Role

    • Use REST Service to Create Registration Request

    • Use REST Service to View Products

    • Request for chat

    Note: A Confirmation dialog appears each time your click Add Privilege to Role. Click OK after adding each privilege.
  11. Click Cancel to close the Add Function Security Policy dialog box.

  12. On the Create Role Self-Service Registration Users page, verify that the privileges that you added are listed, then click Next.

  13. Create the View All Accounts and Contacts security policy:

    1. Click Create Data Security Policy.

      The Create Data Security Policy. dialog appears.

    2. In the Policy Name field, enter the following text:

      View All Accounts and Contacts

    3. In the Database Resource field, search for and click the following resource, then click OK:

      Trading Community Party

    4. In the Data Set list, select All values.

    5. In the Actions list, select the following options:

      • View Trading Community Person

      • Read

      • View Trading Community Organization

    6. Click OK.

  14. Create the View Service Categories security policy:

    1. Click Create Data Security Policy.

      The Create Data Security Policy. dialog appears.

    2. In the Policy Name field, enter the following text:

      View Service Categories

    3. In the Database Resource field, search for and click the following resource, then click OK:

      Service Category

    4. In the Data Set list, select Select by instance set.

    5. In the Condition Name list, select Access the service category for table SVC_CATEGORIES for all customer relationship management service categories.

    6. In the Actions list, select the following option:

      • View Service Category

    7. Click OK.

  15. Create the Grant on Self Service Registration security policy:

    1. Click Create Data Security Policy.

      The Create Data Security Policy. dialog appears.

    2. In the Policy Name field, enter the following text:

      Grant on Self Service Registration

    3. In the Database Resource field, search for and click the following resource, then click OK:

      Self Service Registration

    4. In the Data Set list, select All values.

    5. In the Actions list, select the following option:

      • Read

    6. Click OK.

  16. Create the Grant on Self Service Role security policy:

    1. Click Create Data Security Policy.

      The Create Data Security Policy. dialog appears.

    2. In the Policy Name field, enter the following text:

      Grant on Self Service Role

    3. In the Database Resource field, search for and click the following resource, then click OK:

      Self Service Role

    4. In the Data Set list, select All values.

    5. In the Actions list, select the following option:

      • Read

    6. Click OK.

  17. Click the Summary step.

  18. Click Save and Close.

    A dialog appears, confirming the role changes.

  19. Click OK.

Create the APPID User

Once you have created the role for the APPID user, you must create the APPID user, and assign the role to the user.

To create the APPID user:

  1. Sign in to Oracle Engagement Cloud.

  2. Navigate to the Security Console work area and click the Users tab.

  3. Click Add User Account.

  4. Enter the values in the required fields.

  5. Click Add Role.

    The Add Role Membership dialog appears.

  6. Search for and click on the the following role:

    Self-Service APPID Users

    Note: This role was created in the Create the Role for APPID User task.
  7. Click Add Role Membership.

    A confirmation dialog appears.

  8. Click OK.

  9. Click Done.

  10. Click Save and Close.

You can create APPID users to have a different password expiry policy. Doing so ensures that the regular password expiry rules do not apply to APPID users. To do this, you can create a different user category for the APPID users.

To create a category for the APPID user a with a different password expiry policy:

  1. Sign in to Oracle Engagement Cloud.

  2. Navigate to the Security Console work area and click the User Categories tab.

  3. Click Create.

    The User Category: Details page appears.

  4. Click Edit.

  5. Enter a name in the User Category Field.

  6. Click Save and Close.

  7. Click Password Policy.

  8. Click Edit.

  9. Configure the fields for the APPID user password expiry policy.

  10. Click Save and Close.

Set Up Administrators and Developers

This topic describes how to set up developers and administrators for Digital Customer Service in Oracle Engagement Cloud.

Create a Developer or Administrator with Appropriate Roles

To work with business objects relevant to Digital Customer Service, the developer must be a Digital Customer Service user and must be granted the appropriate roles.

To create a Digital Customer Service developer or administrator, follow the instructions in these tasks:

  1. Create an Internal Customer Account

    Note: This task is completed only once. The following two tasks must be completed for every Developer or Administrator.
  2. Create a Self-Service User Account for the Developer Through REST API

  3. Approve the User

  4. Assign the DCS Developer Role

Create an Internal Customer Account

Before creating the Digital Customer Service developer or administrator users, an internal customer account must be created for use by these users. The internal customer account lets you associate your staff to a specific account. An account key is required when creating a new Digital Customer Service user.

Note: You only need to create the internal customer account once. This internal customer account can be used by all Developers and Administrators.

To create an internal customer account:

  1. Sign in to Oracle Engagement Cloud.

  2. Navigate to the Service work area and click Accounts.

  3. Click Create Account.

  4. Enter the Name.

    Note: The name that you enter in this field represents the AccountKey that you need to use in the Create a Self-Service User Account for the Developer Through REST API topic.
  5. Select Customer from the Type menu.

  6. Click Save and Close.

Create a Self-Service User Account for the Developer Through REST API

Creating a self-service user account for the developer can be done using REST API. This task will require the use of Postman or another REST API Tool.

The following table lists the parameters and associated values that are needed to create a self-service user account for a developer through REST API:

Parameter Value

url

.../crmRestApi/resources/11.13.18.05/selfRegistrations

Authorization

Basic Auth

Username

The user name of the user that you created in the Create an Internal Customer Account topic.

Header

Accept - application/json
Content-Type - application/vnd.oracle.adf.resourceitem+json

Action

Post

Payload

{
	"AccountKey" : "<internal_customer_account>",
	"EmailAddress" : "<user_email@companydomainname.com>",
	"LoginId" : "<user_login>",
	"PersonFirstName" : "<user_firstname>",
	"PersonLastName" : "<user_lastname>"
}

Where the <interal_customer_account> is the internal customer account that you created in the previous task. The same internal customer account can be specified for all Administrators and Developers. The <user_login> is the ID that you want to use to sign in. The <user_email@companydomainname.com> is the email of the Digital Customer Service user that you're creating.

For example, you can create Jane Smith, a self-service user account for the developer through REST API, by running the following command in Postman:

Note: In this example, the login ID is specified. If the login ID isn't specified, the value used is the value that's assigned to the SVC_CSS_SIGN_IN_ATTR_NAME profile option.
curl -v -u user:pppssswww -X POST \
  https://mydepoloyment.mycompanydomain.com/crmRestApi/resources/11.13.18.05/selfRegistrations \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/vnd.oracle.adf.resourceitem+json' \
  -d '{
      "AccountKey": "My Company",
      "PersonFirstName": "Jane",
      "PersonLastName": "Smith",
      "EmailAddress": "jane.smith@mycompanydomain.com",
      "LoginId": "jane.smith"
}'
Note: Run this command using the previously created APPID user.

The user will be created with a Status of Pending if the auto-approve feature is disabled.

Approving the User

Once the Administrator or Developer user is created, it remains in a PendingStatus until it's approved in Oracle Engagement Cloud. You must approve the user, then you must assign the appropriate role.

Note: If it's the first user approved for this account, the user will automatically have the account administrator role. For all subsequent users, the Account Administrator role must be assigned.

For more information about approving the user, refer to Managing Registration Requests. For more information about assigning the Digital Customer Service Account Administrator role, refer to Managing Self-Service Users.

Assign the Customer Self-Service Application Developer Role

Once you have approved the user, you must assign the Customer Self-Service Application Developer role to the user. The Customer Self-Service Application Developer role allows the user to approve registration requests and consult the security console to verify if a user has been created.

To assign the Customer Self-Service Application Developer role:

  1. Sign in to Oracle Engagement Cloud.

  2. Navigate to the Security Console work area and click the Users tab.

  3. Search for the user that you created in the Create a Self-Service User Account for the Developer Through REST API section.

  4. From the search results, click the user.

  5. Click Edit.

    The Edit User page appears.

  6. Click Add Role.

    The Add Role Membership dialog appears.

  7. Search for the following role:

    Customer Self-Service Application Developer

  8. Click Add Role Membership.

    A confirmation dialog appears.

  9. Click OK.

  10. Click Done.

  11. Click Save and Close.

Set Up Oracle Identity Cloud Service

Enable and Perform a User Synchronization

This topic describes how to enable and perform a synchronization in Oracle Identity Cloud Service.

Complete the following task in Oracle Identity Cloud Service:

  1. Enable and perform a user synchronization.

    For instructions about completing this task, refer to Enable Synchronization from Oracle Fusion Applications Cloud Service to Oracle Identity Cloud Service with Oracle Fusion Applications Cloud Service as the Identity Provider in the Related Topics.

    Note: Complete the steps in the Enable Synchronization by Modifying the Oracle Fusion Application in Oracle Identity Cloud Service sub-topic only, and ensure that Authoritative Sync is selected when defining the synchronization type. The Obtain the External Host Name and Port Number of Your Oracle Fusion Applications Cloud Service sub-topic and the Create a New Oracle Fusion Application in Oracle Identity Cloud Service sub-topic need not be completed because the application entry was already created when provisioning.

Create a Non-Federated User Account for Developers

After performing a user synchronization, a non-federated user account must be created in Oracle Identity Cloud Service for use with Oracle Developer Cloud Service. This topic describes how to create the non-federated user for developers.

A non-federated user account is required in Oracle Identity Cloud Service for users, such as developers, that need to authenticate to Oracle Developer Cloud Service to use the Git integration for managing source code.

Note: Follow the instructions in this topic only if your developers intend to use Git.

In subsequent topics, the developer will need to provide their credentials to authenticate to Oracle Developer Cloud Service. You can only authenticate to Oracle Developer Cloud Service with non-federated user accounts in Oracle Identity Cloud Service. The topics in which the developer credentials will be required are: Configure Git and Set Up Oracle Visual Builder.

To define a non-federated user for developers:

  • If the user doesn't yet exist, add the user by following the instructions in Creating User Accounts in the Related Topics.

  • If the user already exists, you must edit an attribute value for the user account by turning on the Federated switch. For more information on editing an attribute, refer to Editing Attribute Values for the User Account in the Related Topics.

Add User Roles

This topic describes how to add roles in Oracle Visual Builder and Oracle Developer Cloud Service to configure proper user authentication for your Oracle Visual Builder platform and editor.

To add user roles:

  1. Add Oracle Visual Builder roles:

    1. Assign the Oracle Visual Builder ServiceDeveloper role for users that require build and maintain access in the Oracle Digital Customer Service applications.

    2. Assign the Oracle Visual Builder ServiceAdministrator role for users that require administrative access to configure instance-wide settings for the Oracle Visual Builder environment for all applications.

    For instructions about completing this task, refer to Assign User Roles in the Related Topics. Additionally, you can learn more about roles and privileges in Oracle Visual Builder by referring to the Privileges Available to Roles in Oracle Visual Builder in the related topics.

    Tip: You can use the filter to help you locate your instance. For Oracle Visual Builder instances you might want to search for the name of your instance prefixed with "VBINST" (for example "VBINST_").
  2. Add Oracle Developer Cloud Service developer roles:

    1. Sign in to Oracle Developer Cloud Service.

    2. From the My Services dashboard, navigate to the Identity Cloud console and click Applications.

    3. Click the link for your Oracle Developer Cloud Service instance.

      You can use the filter to help you locate your instance. For Oracle Developer Cloud Service instances you might want to search for your instance prefixed with "DevServiceAppAUTO".

    4. Click the Application Roles tab.

    5. Grant a role to users:

      1. Click the menu options icon shown next the role, and select Assign Users. If you want to assign the role to a group, you need to select Assign Groups.

      2. Select the check box next to the name of each user that you want to add to the role, and then click Assign.

      Note: You will need to add the DEVELOPER_USER or the DEVELOPER_ADMINISTRATOR user roles. For more information about these roles, refer to the Identity Domain Roles in the Related Topics.

Set Up Oracle Visual Builder

Configure Oracle Visual Builder with Oracle Engagement Cloud

This topic describes how to configure Oracle Visual Builder with specifics about Oracle Engagement Cloud.

To specify Oracle Engagement Cloud details in Oracle Visual Builder:

  1. Sign into Oracle Visual Builder as an administrator.

  2. Click the Menu icon, and select Settings.

    The Tenant Settings page appears.

  3. Specify the Oracle Engagement Cloud details in the Fusion Applications Cloud Service section:

    • In the Fusion Applications Base URL text box, enter Oracle Engagement Cloud URL.

      For more information about base URL, refer to Add a Connection for Applications Services in the Related Topics.

Configure Oracle Visual Builder with Oracle Component Exchange

This topic describes how to configure Oracle Visual Builder with specifics about Oracle Component Exchange.

Specify Oracle Component Exchange Details

This topic describes how to configure Oracle Visual Builder for use with Oracle Component Exchange.

By default, the values are populated. For more information, refer to the Add a Connection to the Component Exchange topic in the Related Topics section.

To specify Oracle Component Exchange details in Oracle Visual Builder:

  1. Sign into Oracle Visual Builder as an administrator.

  2. Click the Menu icon, and select Settings.

    The Tenant Settings page appears.

  3. Specify the Oracle Component Exchange details in the Component Exchange section:

    Note: By default, the detail values are populated. For more information, refer to the Add a Connection to the Component Exchange topic in the Related Topics section.
    1. In the Service URL text box, enter Oracle Developer Cloud project URL, using the following format:

      https://<host>/profile/<org>/s/<org>_<project-id>/compcatalog/<version>/
    2. In the User name text box, enter an Oracle Developer Cloud administrator user.

    3. In the Password text box, enter an Oracle Developer Cloud administrator user password.

Create a New Digital Customer Service Application

This topic describes how to create a new Digital Customer Service application in Oracle Visual Builder.

To create a new Digital Customer Service application:

  1. Sign in to the Oracle Visual Builder editor as a user with the Developer role.

  2. Click New.

    The Create Application dialog appears.

  3. In the Application template section, click Change template.

  4. Click the most recent version of the Digital Customer Service Reference implementation for Engagement Cloud tile.

    This template creates an application with basic service functionality, including the ability to create and update SRs, search knowledge, and chat with an agent.

  5. Click Use selected.

  6. Specify the Application Name.

  7. Specify the Application ID.

    The Application ID is automatically derived from the specified Application Name, but you can change it, if desired. The Application ID cannot be modified once the application is created: it appears in the application URL.

  8. Click Finish.

    The Digital Customer Service application has been created. You are now ready to configure your Digital Customer Service application to meet your business needs.

Note: When Oracle Engagement Cloud is deployed with multiple business units, additional configuration is required. For more information, refer to the Configuring Multiple Business Units with Digital Customer Service topic in the Related Topics.

Add Mappings to User Roles

After creating your Digital Customer Service application, you must add the following mappings to your user roles in Oracle Visual Builder:

  • Customer Self-Service User

  • Customer Self-Service Administrator

To add the required Oracle Identity Cloud Service role mappings to your application roles:

  1. Sign in to Oracle Visual Builder.

  2. Open your Digital Customer Service application.

  3. Click the Menu icon and select Settings.

  4. Click the User Roles tab.

  5. Add the Customer Self-Service mapping:

    1. Hover over the User user role, then click the Pencil icon.

    2. Click in the Mapping list.

      A list of available mappings appears.

    3. From the Mapping list, select Customer Self-Service User.

    4. Click the Check Mark icon.

  6. Add the Customer Self-Service Administrator mapping:

    1. Hover over the Account_Administrator user role, then click the Pencil icon.

    2. Click in the Mapping list.

      A list of available mappings appears.

    3. From the Mapping list, select Customer Self-Service Administrator.

    4. Click the Check Mark icon.

Set Up Authentication for Your Application

For your application to run properly, you must first set up system-to-system authentication between your Digital Customer Service application and Oracle Engagement Cloud.

To complete the tasks in this topic, you must be signed in to the Oracle Visual Builder with a valid developer or administrator account. This account was created in the previous topic. For more information about the developer user account that you created, refer to the Setting Up the APPID User, Administrators, and Developers topic earlier is this chapter.

To set up authentication, perform the following tasks:

  1. Open your Digital Customer Service application in the Oracle Visual Builder.

  2. Click Service Connections.

  3. Configure authentication for Sales and Service:

    1. Click Sales and Service.

      The Sales and Service tab opens.

    2. Click the Authentication tab.

    3. Select Oracle Cloud Account from the Authentication Mechanism list.

    4. Select the Allow anonymous access option.

    5. Select Basic from the Anonymous Authentication Mechanism list.

    6. In the User name field, enter the user name of APPID user.

      Note: You created the APPID user when setting up the APPID user, administrators, and developers. For more information, refer to the "Setting Up the APPID User, Administrators, and Developers" topic.
    7. In the Password field, enter the password of APPID user.

      Note: You created the APPID user when setting up the APPID user, administrators, and developers. For more information, refer to the "Setting Up the APPID User, Administrators, and Developers" topic.

Configure Git

This topic describes how to configure Git for source control of your application.

In some deployments, you might have multiple Oracle Developer Cloud Service instances available to you within your account on Oracle Cloud. Oracle recommends that you use only one instance that includes the following string in the label or name: test. Using only one version that includes the test string enables better source code management within a single instance. This is recommended because, in the future, your account on Oracle Cloud will allow you to view only one test instance of Oracle Developer Cloud Service. Moreover, other instances that include test with be made obsolete, and will be subject to removal.

To configure Git, follow these steps:

  1. In Oracle Developer Cloud Service, set up a Git repository. For more information about setting up a Git repository, refer to the Related Topics. After performing this task, you will receive an email informing you of the Oracle Developer Cloud Service URL.

    Note: For groups that will be collaborating, when you're creating your project, select the Shared option when defining Security.
  2. In Oracle Visual Builder, integrate your application with a Git repository. For more information about integrating your application with a Git repository, refer to the Related Topics.