Access control for Bitbucket projects

[Ramana Rainn]

We are currently using Bitbucket 4.13 version on on-premise server. We use AD groups for user access and these AD groups have been added to local groups where we control the access option.

Now we would like to control the access for different projects so that they can see only respective projects, not other one. I gave access to one local group to Bitbucket users, Project Creator access in global permissions and same local group has given admin to one specific project and kept default permission as no access for this project. But users can see all the projects on server.

Can you please advise on how to fix on this.

[Julius Davies [bit-booster.com]]

It might be a problem with group-based global permissions.  Does your instance have a "stash-users" or "bitbucket-users" local group defined?  (But not in AD --- this group is typically local to Bitbucket only).

What are the global permissions for that group?

That's my shot-in-the-dark theory.  But hard to say; you have not provided enough information for me to better diagnose the problem.

If the problem is coming from the default "stash-users" group, then you might find this related Question & Answer thread useful:  https://community.atlassian.com/t5/Bitbucket-questions/Stash-Project-Permissions/qaq-p/838250

[Ramana Rainn]

Thanks for quick response. We do have Stash Users as local group and this group has bitbucket user permission on global permissions.

I am adding all AD groups to Stash-Users and custom local group.  I have given custom local group to admin access on specific project. Am i missing something?  or let me know if you need anything.