diff options
| author | mo khan <mo@mokhan.ca> | 2025-05-02 14:29:41 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-05-02 14:29:41 -0600 |
| commit | c583bcd1473205104a1e1af812ed4976d30c7baa (patch) | |
| tree | 933edf78a4ac8aea55256e42641e56bbb4c58834 /doc/share/authz/FAQ.md | |
| parent | 91defaefca47e9cebbe92c6abf33c4423df9bc7d (diff) | |
refactor: remove anything unrelated to the authz daemon
Diffstat (limited to 'doc/share/authz/FAQ.md')
| -rw-r--r-- | doc/share/authz/FAQ.md | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/doc/share/authz/FAQ.md b/doc/share/authz/FAQ.md deleted file mode 100644 index 8e73beb2..00000000 --- a/doc/share/authz/FAQ.md +++ /dev/null @@ -1,33 +0,0 @@ -# Frequently Asked Question (FAQ) - -* Q: Are there permissions that do not cascade down the group hierarchy? -* Q: How do we define the scope of a permission? (hierarchical?) -* Q: What is the unique identifier for each security principal across service boundaries? (i.e. bigint, ulid, uuid, email) -* Q: What permissions do each of the standard roles have today? -* Q: How does a permission cascade down a group hierarchy? - -``` -Organization - Group A - * Roles - * Developer - * Maintainer - * Custom A - * base: developer - * permissions: - * admin_vulnerability: true - * read_vulnerability: true (implicitly) - * Custom B - * base: maintainer - * permissions: - * Doesn't really matter because Maintainer has all the permissions available via a custom role. <- Fact check this - Group Aa - Project Aa1 - Project Aa2 - Group Aaa - Project Aaa1 - Project Aaa2 -``` - -* Q: If a user has a membership at `Group A`, does the permissions associated with that -membership cascade down to `Group Aa` and `Group Aaa`? |