chore: merge project permissions into advanced permissions #28115
+25
−77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Follow along on RBAC: #24512
Billing PR to be shipped after this: https://github.com/PostHog/billing/pull/1092
Deprecating
project_based_permissioning
and merging intoadvanced_permissions
.Currently
advanced_permissions
is used for dashboard permissions andproject_based_permissioning
is used for permissions around projects like private projects. With the new RBAC / access control system we are merging these together and they will be available on the teams add-on.Since both of these are available on the same plans right now, this should have no affect to users. I confirmed that every plan that has
advanced_permissions
also hasproject_based_permissioning
and vice versa.👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
It doesn't have an impact.
How did you test this code?