Skip to content

Create global teams which could be used by each organization #23262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
KroMignon opened this issue Mar 3, 2023 · 2 comments
Closed

Create global teams which could be used by each organization #23262

KroMignon opened this issue Mar 3, 2023 · 2 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@KroMignon
Copy link

KroMignon commented Mar 3, 2023 •
edited
Loading

Feature Description

My original concern was to find a way to made all repository (even privates) listable for each registered user cf. feature request #23117 (as I could not reopen the FR, I create a new one).

@wolfogre suggests my to use teams for this, which is a good way to solve my issue but it is not very "comfortable" to use. Because those teams have to be created for each organization and when a new user have to be added, it must be done for each organization!

It is possible to create a kind of "default/global/template teams", which could be used by each organization?

For example, a Gitea admin user creates global teams with default allowed accesses.
Then for each organization, those "global teams" are visible and could be used as they are or with"adjusted" allowed accesses.

This will allow administrators to managed those global teams, and all changes will be applied to any organization which uses those teams.

Is this feasible or will it break Gitea?

Screenshots

No response
@KroMignon KroMignon added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Mar 3, 2023
@lunny
Copy link
Member

lunny commented Mar 3, 2023

Is this a duplication of #3642?

@KroMignon
Copy link
Author

@lunny Yes! This is exactly what I need.
Sorry for the noise, haven't see it.

Is this FR still "alive", is there a chance it could be implemented in a future release of Gitea?

@lunny lunny closed this as completed Mar 3, 2023
@lunny lunny added issue/duplicate The issue has already been reported. and removed type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Mar 3, 2023
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lunny @KroMignon