Our company works on several projects for different clients. We have clients that want to browse and freelancers that work on different projects.
This caused me to play around with permissions as the default was that every user had access to everything meaning some clients could see projects they shouldn't.
Now a new freelancer is working with us on a project and I find myself confused on how to handle permissions.
Should I create a new scheme just for him or add him to the group I created for a client?
What is best practice in this case?
Thanks in advance.
>The default was that every user had access to everything meaning some clients could see projects they shouldn't.
Yes, I'm afraid you will want to unpick that. The usual problem is that the default is to add users to the group that says "can log in and use the system", but that group is also used in project roles to say "this group are users of this project", which then, of course, dumps everyone into all your projects.
Have a look at your permission schemes and see what the rule is for "browse project". By default, it'll be a role, but there may be more. Then, for each project, look at that role and remove anything that grants wide access, replacing it with narrower groups or individual users, so that your existing users can still use the project. You'll then be able to add your freelancer to just the projects they need to see.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs