Authorize VB Studio to Access Visual Builder and Integration Instances

You may be required to authorize VB Studio to access Oracle Visual Builder and Oracle Integration instances that are connected to your OCI account. This authorization allows users to view Visual Builder and Integration instances linked to the OCI account and create environments with these instances.

So when might you need to do this? Mostly when your VB Studio instance is using the built-in Free VM account—but there are several other scenarios when VB Studio isn't authorized to access the Visual Builder and Integration instances linked to your OCI account. Therefore, it's recommended that you always check your VB Studio instance's details to make sure the policy statement that enables this access is correctly defined.

Open the OCI console and click Navigation Menu in the upper-left corner.
Select Identity & Security, then under Identity, select Policies.
From the Compartment list on the left side of the Policies page, select the root compartment.
Check if a VB Studio policy has been defined to include the statements granting read permissions for visualbuilder-instance and integration-instance resources.
If a policy exists but is missing one of these statements, update it to include all these statements; if a policy does not exist, create one to include all these statements in this format:
```
Allow any-user to inspect all-resources in tenancy where request.principal.id in ('<VBS_instance_OCID>')
Allow any-user to read visualbuilder-instance in tenancy where request.principal.id in ('<VBS_instance_OCID>')
Allow any-user to read integration-instance in tenancy where request.principal.id in ('<VBS_instance_OCID>')
```
If you have multiple VB Studio instances (say, because each TEST and DEV instance in your Oracle Cloud Application environment family got its own instance of VB Studio), enter all their OCIDs as a comma-separated list within single quotation marks ('), for example:
```
Allow any-user to inspect all-resources in tenancy where request.principal.id in ('ocid1.vbsinstance..abc', 'ocid1.vbsinstance..xyz')
Allow any-user to read visualbuilder-instance in tenancy where request.principal.id in ('ocid1.vbsinstance...abc', 'ocid1.vbsinstance...xyz')
Allow any-user to read integration-instance in tenancy where request.principal.id in ('ocid1.vbsinstance...abc', 'ocid1.vbsinstance...xyz')
```
Here's how you can retrieve your VB Studio instance's OCID:
1. In the navigation menu, select Developer Services and Visual Builder Studio.
2. Select the root compartment and access your VB Studio instance's details.
3. Copy the instance's OCID shown under Instance Info.
Note

It's important to use the same format as your existing policy. This format depends on when and how your OCI account was configured. So if CI/CD authorization for your OCI account was enabled some time ago, you may see an older format with statements like (for example) Allow service vbstudio. In this case, update your policy to include the missing statements in the same format:
```
Allow service vbstudio to inspect all-resources in tenancy
Allow service vbstudio to read visualbuilder-instance in tenancy
Allow service vbstudio to read integration-instance in tenancy
```

Oracle Cloud Infrastructure Documentation