Setting up Group and Project Hierarchy
Organizing your environment
Projects and groups are the building blocks of your GitLab environment.
- Projects: Designate a home for your files and code or track and organize issues within a business category
- Groups: Organize a collection of users or projects. Use these groups to quickly assign people and projects.
- Permissions: Define user access and visibility for your projects and groups.
Watch: Groups and Projects Basics
3 ways to manage access
- Grant team access to a set of resources. Designate specific groups that contain subgroups/projects only and others that include users (“members”)
only. Then, assign your user groups to subgroups/projects.
- Use case: Run multiple Agile teams with microservices.
- Benefit: Add a group of users to a project with a single action.
- Get started: Manage project access by team.
- Sync group memberships via LDAP. Automatically integrate your LDAP groups with GitLab Enterprise Edition (self-managed only).
- Use case: Auto-sync GitLab group memberships with LDAP group members.
- Benefit: Get more control over per-group user management.
- Get started: Sync groups with LDAP.
- Implement a top-level structure. Manage user access
with inherited permissions. Use up to 20 levels of subgroups to organize
both teams and projects.
- Use case: Align user access with business objectives (e.g., teams, cost centers, product lines) by creating subgroups that act as categories.
- Benefit: Give group members more control over project management.
- Get started: See nested category examples.
Your project/group checklist
- Create a new project.
- Create a new group.
- Add members to the group.
- Create a new subgroup.
- Add members to the subgroup.
- Enable external authorization control.