Implement teams/organization concepts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Now that RBAC is released into 3.4 there should be a good way to be able to separate out specials actions, workflows, and rules to that team/org. This gives greater granularity for access control and separates team members from accessing other team member's rules.
Right now the only work around I can think of is to create a dummy pack or some kind that would belong to role(s), which I haven't really tested. While this is probably doable, its doesn't seem like a very clean way of doing it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing RBAC implementation released in 3.4 and trace how access is applied to actions, workflows, and rules. Clarify the intended team and organization model, including how members should be separated from other members' rules and whether the dummy-pack workaround is relevant. Done criteria are not defined in the issue, so the scope and acceptance tests need agreement first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100