Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Why user from one instance of VBS is available in another instance VBS as a team member or owner

In Organization we are working on more than one Fusion instances and VBS instances. In one VBS instance we can able to see users from other instances when we try to add team member in VBS project, and system is even allowed us to add those different instance user as well, why it is allowed and what intention is behind this?

Also when we added other instance user as a team owner he can able to see this project in that VBS instance where that user is belong and asked to create Environment for that instance from the project is belong. If we create environment then does that project get created in user's instance with new GIT repository and does it created new package and deployment build jobs ?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!