How Are Users Impacted by Multiple VB Studio Instances?

Visual Builder Studio team members have different user names when functioning in the common VB Studio organization with multiple instances of VB Studio.

To enable cross-instance collaboration, a single user is assigned a unique name to reflect the environment where the user was created. For example, UserA in the development instance DEV1 might be known as UserA@<Oracle Cloud Applications-instance-name>-DEV1 to VB Studio, UserB might be UserB@<Oracle Cloud Applications-instance-name>-DEV2, and so on. These user names are assigned by VB Studio automatically when your instances are provisioned. This means that if you log on to the VB Studio associated with your DEV instance, for example, you will not see the workspaces you created when you were logged on to a different DEV instance or, say, to your TEST instance.

Suppose a user in DEV pod DEV1 has the user ID tina@myinstance. This user is not a member of any VB Studio projects. When she clicks Edit Page in Visual Builder Studio from her Oracle Cloud Application, VB Studio creates a new project, and adds the user to the project as tina@myinstance-DEV1. She is also automatically made the project owner. If she wishes to transfer those responsibilities to another user, she can do so, but she has to wait until there is at least one other project member. Each project must have at least one owner.

All users who have the VB Studio IDCS role DEVELOPER_ADMINISTRATOR—or a CRM or HCM Administrator role—on any of the instances in the environment family, automatically become a VB Studio organization administrator and enjoy all the privileges inherent to that role. (See Manage the Organization for information on what an org admin can do.)