User/Permission groups

[mattpenn20]

Description

Having quite a few users on my seerr instance can often lead to a lot of overhead managing users and ensuring their permissions and requests levels align with the buckets that I have my users in.

It is currently very manual to change many users permissions at once for request levels and approvals.

Desired Behavior

I would love the ability to apply or attach users to "configuration groups", where settings made in the configuration group are attached to every user within it.

For example - a custom "4k requester" group could be applied to 3 users, and each of those 3 users would get the ability to request 4k content.

For additional granularity if the idea gains traction, it would be nice to have individual overrides for users, where the configuration group is applied to all users within it, but any changes directly to the user supersede the configuration group.
This piece of the request may be beyond scope, or add unnecessary overhead.

Additional Context

No response

Search Existing Issues

• Yes, I have searched existing issues.

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[aussierk]

I want to ensure I understand the request well as it may be a good idea, however only after the implementation of OIDC.

Are you suggesting group mappings essentially being able to map certain groups of users to a specific set of default permissions that defer per group?

I think you additional granularity can be easily handled within the implementation of the first idea.

That being said, implementing user groups and group management within Seer itself without OIDC is more in the periphery of the main goals of Seer so I think likely need to be an OIDC only (or at least first) feature.

[mattpenn20]

I want to ensure I understand the request well as it may be a good idea, however only after the implementation of OIDC.

Are you suggesting group mappings essentially being able to map certain groups of users to a specific set of default permissions that defer per group?

I think you additional granularity can be easily handled within the implementation of the first idea.

That being said, implementing user groups and group management within Seer itself without OIDC is more in the periphery of the main goals of Seer so I think likely need to be an OIDC only (or at least first) feature.

That is exactly accurate to what I am hoping for.

Definitely seems like it would mesh well with OIDC.

[aussierk]

That makes sense, I think it would be interesting to implement once we have OIDC implemented.