Former employees has access to repositories in team

[Martin Huber]

Hi,

all our former employees (sure, removed from team) has access to all repositories they created in the team in Bitbucket.

I know, settings > user and group access > delete the user in the user section from repository.

But: no, we have about 600 private repositories and it is not possible to inspect every repository after a employee change.

Is there a way to prevent this behaviour? And is it possible to delete former employees automatically?

Greets,
Huaba

[Martin Huber]

I think it's similar to this issue: https://bitbucket.org/site/master/issues/5148/repos-transferred-to-a-team-retain-creator

[Martin Huber]

No suggestions to solve this? Or any hint for settings to solve this?

[Christian Glockner]

Hi Martin,

Just to be sure - is this about Bitbucket Server or our Cloud service bitbucket.org?

Cheers,

Christian

Premier Support Engineer

Atlassian

[Martin Huber]

Cloud service bitbucket.org

[lumoura]

Hi Martin ,

On Bitbucket Cloud you can organize your team in groups, and then add this groups to your repositories.
You can read more about this on the link below:
https://confluence.atlassian.com/bitbucket/organize-your-team-into-user-groups-665225542.html

[Martin Huber]

Yes, i know and we do it so!

But the creator of a repository is listed in the section "Users" and has always admin rights. If this person leaves the company and removed from the team, it has furthermore admin rights on repositories created by himself. Thats bad...

[lumoura]

Since you are working as a team, you can create repositories under the team account.

ON the image provided by you the user that still have access to the repo, is the one that is mentioned as "owner"?

Furthermore, you can request him to transfer the repository to the team.

Best regards. 

[Martin Huber]

No, the owner is the team, the second entry with admin rights is the user which created this repository.

And this entry (user with admin rights) still exits, after removing it from the team. So this user have access to the repository although he is no longer in the team.

Thanks for help.