django-guardian VS django-fsm

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

These pieces fit together very well and are sufficient for replacing most of the goodies Django provides. However, there's one piece missing. Django has a built-in permissions feature, but it's limited to model-level control, i.e., if a user or group has X access to model type Y. Many users have been using the popular django-guardian package to implement row-level permissions. It allows you to establish permissions between users/groups and objects, manages the underlying permission database tables, and provides APIs for configuring and checking such permissions.

https://github.com/django-guardian/django-guardian/issues?q=is%3Aopen+is%3Aissue+label%3ABug

Could use django-guardian for this instead: https://github.com/django-guardian/django-guardian

I was about to use django-guardian until I came across the following in the official documentation:

django-guardian for per object permissions

I'm currently logging status changes to several models in my Django REST API using the django-fsm and django-fsm-log packages. However, all of the logs are stored in a single table. This is gonna end up being a massive table that will take time to run through to do analysis and reporting. To make it easier I'd like to either break out the logging table by each individual model or sort them by the highest level model that's associated. I'll explain what I mean.

...see https://github.com/viewflow/django-fsm

django-fsm - State management and transitions.