In general we've avoided adding this sort of permissions and policy,
since it adds a lot of UI complexity for what is essentially a
sociology problem. We have a bug open requesting some sort of general
policy set-up (while we try to figure out what that means), but I'd
recommend that this is better enforced through training and
management. If people are submitting code without the proper
authorizations, then a check-box isn't going to stop them.
On Wed, Feb 3, 2010 at 5:00 PM, Jennifer <quyr...@yahoo.com> wrote:
> Is there a way to restrict access to the ship it checkbox? We want
> everyone to be able to post reviews, but only allow authorized people
> to check "ship it". I tried making an auth group, but could find no
> permission for the "ship it" checkbox.
> We have a list of projects and which team leaders are allowed to
> approve code changes for that project. The problem is that even
> though we tell team members not to check the box, they do anyways,
> then the submitter will check in his code. I know reviewboard does
> not stop checkins, but we would like to stop unauthorized people from
> checking the "ship it" checkbox.
> PS thanks to everyone who is working on reviewboard. It has helped
> our codebase immensely.
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at