How should team repositories be created and managed?

We’re just getting started with GitLab. We’re not ready to commit for a supported version yet but we want to get as much as possible out of the community supported version.

My question is about team development. While individuals may have their own personal repos, we need our business apps to not be tied to an individual developer’s repository; they should be in a team repository. How are other companies handling that? Are you creating a “functional” account and using that for a shared repository space?

Are you familiar with groups?

1 Like

Thanks, Axil. Clearly I wasn’t familiar enough with groups. I thought of that topic as simply managing access and hadn’t looked there for this answer. It’s a pretty good start. Of course I’d still love to hear from users with their own use cases/stories on this.