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.

Restrict certain VBS project users to only package and deploy but not change other artifcats

Summary:

Segregation of duties for deploying the VBS projects

Content (please ensure you mask any confidential information):

We have a different team currently in place, who is responsible for deploying the release items to higher instances for Fusion HCM changes for sanbbox or FSM packages. Similarly, for VBS projects, we want to have these members added to project but only should have access to deploy jobs but no other access should be given such as Workspace, git, etc etc.

Can you guide which role will full fill my requirement.

@John Rhodes-Oracle

Version (include the version you are using, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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