[GH-ISSUE #239] Restrict users from accessing games #125

New Issue

2026-02-17T17:06:12-05:00

yindo commented

2026-02-17 17:06:12 -05:00

Originally created by @Huskydog9988 on GitHub (Sep 4, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/239

Not every instance admin will want every user on int to be able to access every game imported. My initial proposition when thinking about this was to restrict user's based on the library source the game came from, but due to how drop is architected, I think instead managing it per game is probably for the best.

To keep managing which user's can access which content simple, and for future expandability, I think implementing a simple rbac system would do wonders for ux. This system should also be extended to allow for a very basic parental control system. In it, games above a certain age rating, like M, could be excluded based on a user's role as well.

Originally created by @Huskydog9988 on GitHub (Sep 4, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/239 Not every instance admin will want every user on int to be able to access every game imported. My initial proposition when thinking about this was to restrict user's based on the library source the game came from, but due to how drop is architected, I think instead managing it per game is probably for the best. To keep managing which user's can access which content simple, and for future expandability, I think implementing a simple rbac system would do wonders for ux. This system should also be extended to allow for a very basic parental control system. In it, games above a certain age rating, like M, could be excluded based on a user's role as well.

yindo closed this issue

2026-02-17 17:06:12 -05:00

yindo commented

2026-02-17 17:06:13 -05:00