We are an agency with many different clients. Each client has their own 'Project' within Bitbucket and within that project are multiple repos. Each Project and each repo are always set to Private. Access is given for our own internal developers on a per-project and per-repo basis.
Sometimes however, our clients need access to their own code that we are hosting for them through our BB account. Recently, granted access for this client into his own project and set of repos. And ONLY his repos.
He responded back saying that he could see all our projects (aka clients). The good news is that he was not able to view any of the repos in any of these projects -- those are all completely hidden and inaccessible.
The problem is him being able to see who else we work with. I would have expected a Private Project to maintain the same visible/hidden nature much the same way that repos do.
I tried creating a specific group to assign only him, and still nadda.
Would a better option be to create a workspace for Client X, instead of a project? This creates other logistical problems though. There are webhooks tied to projects and moving them from one workspace to another would break that linkage. Also... it's not often that we have clients asking for access, so they are (by default) setup within our Project/Client process.
Anyway... thoughts? Is it even possible to make a Project truly private and invisible?
