To develop visual applications using a VB Studio instance that's in a different identity domain than your Visual Builder instance (for example, a VB Studio instance provisioned in your Oracle Cloud Application account), you'll need to add a Visual Builder instance to your VB Studio project.

1. After you've set up VB Studio to develop visual applications, follow the steps in the this table to set up the project, configure the deployment job, and add users to the project:

   Action	How to
   1. Create an empty VB Studio project.	Sign in to VB Studio. See Access VB Studio from the Oracle Cloud Home Page. On the Organization page, click + Create. On the Project Details page, enter a unique name and description for the project. In Security, select the project's privacy setting. A private project is accessible to invited users only. Users who aren't invited can't access it or make changes to it. You can invite users after creating the project. A shared project is accessible to all users of the organization. Any user can view the source code, create or update issues, edit wiki pages, and interact with project builds. However, only invited users can make updates to the source code in Git repositories, create and run build jobs, and perform deployment operations. In Preferred Language, specify the language for the email notifications your project users will receive. You can change the language in which the user interface appears in your user preferences. Click Next. On the Template page, select the Empty Project template, then click Next. On the Properties page, select the wiki markup type, then click Finish. After the project is provisioned, the Project Home page opens where you can see a summary of the project's provisioning activities; default environment; default workspace; and Git, Maven, and NPM repositories. Review the activities feed and the Environments box for any errors.
   2. In the project, create an environment with your Visual Builder instance.	In the navigation menu, click Environments , and then click + Create Environment. In Environment Name and Description, enter a unique name and description, and click Create. In the Service Instances tab, click Add Instance. For Instance Type, select the Visual Builder, and for Authentication Method, select Visual Builder Credentials. In Base URL, enter the Visual Builder instance's URL. The Instance Name is automatically filled, but you can update that if you wish. The Instance Name will be displayed in the Service Instances tab. In Username and Password, enter the credentials of a user who can access the Visual Builder instance. Click Add.
   3. When users are ready, they can create this workspace in the project.	In the navigation menu, click Workspaces . Click New and select New Visual Application. In Workspace Name, add a name for your workspace. In Development Environment, select the environment you created in the previous step. In Visual Application Template, don't change the default (Default VBCS Application). In Git Repository, select Create new repository, and enter a repository name and working branch name.
   4. The user that created the visual application will need to configure their deployment job.	In your Visual Builder Studio navigation menu, click Builds . Click Configure, then click Configure. Click the Steps tab. In Target Instance, make sure that the environment you created in Step 2 is selected. In Username and Password, enter yours or a user's credentials who can connect and deploy to the Visual Builder development instance. The credentials will be used when the package and deploy build pipeline runs. (Optional) Choose Use custom file names and add custom file name details. (Optional) To overwrite the application's default version, specify the new version in Application Version. Leave it empty to use the version defined in the application's visual-application.json file. Don't deselect the Include the application version in the URL check box. (Optional) In Application Profile, specify the development application profile. Leave it empty to use the application's default profile. Using application profiles, you can define different combinations of servers and security settings for each of your environments, and use them when deploying the application to an environment. To learn more, see What Are Application Profiles? (Optional) To use the existing application's database, in Data Management, select Keep existing environment data. To use a clean database for the application, in Data Management, select Use clean database. Click Save.
   5. Add users to the project.	To allow your team members to access the visual application project, invite them to join the project. See Add Users to the Project.