Skip to content

Commit

Permalink
chore: update group docs to describe subgroups and inherited roles
Browse files Browse the repository at this point in the history
  • Loading branch information
smlx committed Oct 11, 2024
1 parent 1cf5c76 commit b2b1881
Show file tree
Hide file tree
Showing 2 changed files with 40 additions and 3 deletions.
37 changes: 35 additions & 2 deletions docs/concepts-basics/building-blocks/groups.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,38 @@
# Groups

_Groups_ are made up of users who have roles. An organization can have one or more groups. Each project can be assigned one or more groups. Groups can be assigned to multiple projects. Groups are created independently of projects, and then assigned to them.
_Groups_ are made up of users who have roles.
An organization can have one or more groups.
Each project can be assigned one or more groups.
Groups can be assigned to multiple projects.
Groups are created independently of projects, and then assigned to them.

Organizations have a quota to limit the number of groups assigned to it. If you need to change the quota, please contact {{ defaults.helpstring }}.
Organizations have a quota to limit the number of groups assigned to it.
If you need to change the quota, please contact {{ defaults.helpstring }}.

# Subgroups

!!! warning
Subgroups and not commonly used in Lagoon, and you probably don't need them.
However, they can be useful in some situations.

Groups can be nested to an arbitrary depth.
Subgroups are groups which are a child of another group.

A user's role in an ancestor group is inherited by descendant groups.

## Subgroups example

Consider this group structure:

``` mermaid
---
title: Subgroup permissions example
---
erDiagram
CompanyGroup ||--o{ DivisionGroup : child
DivisionGroup ||--o{ TeamGroup : child
```

If a User has `maintainer` role in the top level `CompanyGroup`, then they will also have `maintainer` level access to projects which are in the `TeamGroup`.

Note that this relationship is indirect: the Project is not in the same group as the User, but because the Project is in a _subgroup_ of the User's group, the User has `maintainer` permissions on the Project.
6 changes: 5 additions & 1 deletion mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,11 @@ markdown_extensions:
- pymdownx.tilde
- pymdownx.tasklist:
custom_checkbox: true
- pymdownx.superfences
- pymdownx.superfences:
custom_fences:
- name: mermaid
class: mermaid
format: !!python/name:pymdownx.superfences.fence_code_format
- tables
- toc:
permalink: "#"
Expand Down

0 comments on commit b2b1881

Please sign in to comment.