feat(auth): add authorization roles #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, all users are considered equal on the service. This means that there is no option to provide separate actions, depending on the authorization of the user.
For example, an admin should have more permissions in terms of settings (OIDC setup).
This issue tracks the work of implementing authorization roles for the service. The actual authorization logic is tracked in #54.
After looking at Mastodon, Lemmy, and Pixelfed, I suggest we take the following global roles to not overcomplicate it:
Previously, in v1.0, we had:
Supporting and customer are dropped for v2, as these are not going to be catered to. Individual supporting memberships will have to be managed someway, but not here.