Hello,
When an authorized user creates a new repo, by default, almost all the groups in the team have access to this repo.
I'd like to find a way to limit this behavior, and to only have the authorized user by default and letting him or the admin managing permissions then.
Today, as I'm the Team admin, I've to check periodically and remove useless groups or permissions.
Could you please let me know an easier way manage this?
Thanks,
Philippe
Hi Philippe,
You'll need to adjust the permissions you're granting to your groups, and make them not have default access to new repos. You can read more about it at Group access on future repositories.
Let us know if you have any questions!
Ana
Hi Ana,
Thanks for your answer.
Yes I realized this way later. However, this behavior doesn't fit my needs,
I know which permissions should have each group, their permissions will never change, so it's why I want to give them by default.
But I want to choose which groups should work on repo A and which group should work on repo B, and I don't want to change any group permissions as they should be always the same redardless the repo.
For example: regardless repositories
Group Test has only read permission
Group Develop has always write access
Group Consumer has only read permission, etc.
Any ideas will be welcome.
Thanks,
Philippe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Follow-up:
Group Consumer doesn't always have access to repositories as Group Test.
Philippe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.