Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7913525
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T13:51:53+00:00 2026-06-03T13:51:53+00:00

Is it possible to prevent users from delivering change sets to a component within

  • 0

Is it possible to prevent users from delivering change sets to a component within a stream ?

For instance, an “Integration” stream should never see any deliver from the developers: only the integration team should be able to modify that “Integration” stream.

And yet, right now, any collaborator of the project area are able to make a repo workspace and, by changing its flow target (i.e. adding that “Integration” Stream and setting it “current“), are able to just deliver to that stream!?

How can I prevent that?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T13:51:54+00:00Added an answer on June 3, 2026 at 1:51 pm

    Yes, but the restriction is rather about authorizing the deliver for anyone having a specific role, rather than restraining just one person by name.
    So if that one person doesn’t have a specific role associated with his/her profile in that Project Area, he/she won’t be able to deliver on that stream.

    You need to add a hook, through the “Operation Behavior” section, for the “deliver (server)” operation. See the illustration:

    hook for deliver

    The hook “Restrict Change set delivery to components in a stream” will allow only the users with the role “release_engineer” (custom role created just for our project) to deliver on the Stream mentioned in the field “Stream”, for the components listed in the “Component / Permissions” array.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is it possible to use the mercurial ACL extension to prevent specific users from
I've setup the following to prevent developers from delivering to a stream if the
Let me know if it's possible to prevent users from opening the same java
Is it possible to prevent user from writing letters to a textbox (i.e. force
Very straightforward: Is it possible to prevent the browser from scrolling when a user
Is it possible to prevent an asp.net Hyperlink control from linking, i.e. so that
Is it possible to prevent the browser from following redirects when sending XMLHttpRequest-s (i.e.
Is is possible to prevent Wget from making an output file when there is
Is it possible to prevent a newer SVN client (say 1.6) from automatically upgrading
Does anyone know if it is possible to prevent a work item from being

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.