Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Launch: Help us enforce maker/checker process

Avatar

Avatar
Shape 100
Community Advisor
Andrew_Wathen_
Community Advisor

Likes

592 likes

Total Posts

328 posts

Correct reply

16 solutions
Top badges earned
Shape 100
Bedrock
Coach
Seeker
Contributor 2
View profile

Avatar
Shape 100
Community Advisor
Andrew_Wathen_
Community Advisor

Likes

592 likes

Total Posts

328 posts

Correct reply

16 solutions
Top badges earned
Shape 100
Bedrock
Coach
Seeker
Contributor 2
View profile
Andrew_Wathen_
Community Advisor

08-02-2018

Currently, the following roles are available:

  • develop
  • approve
  • publish

I want to be able to stop people approving code that they have developed themselves.  However, our team is not big enough that we can afford to have mutually exclusive groups of developers and testers.  Therefore, I have to give 'develop' and 'approve' rights to everyone, which mean users can effectively mark their own homework.

What I would like is an additional 'approve' permission which only allows a user to 'approve' libraries submitted for approval by other users  i.e. they can 'approve' other peoples code for publishing, but not their own.