What's the purpose of this library?

[MuriloScarpaSitonio]

I came across this library reading a newsletter and I wasn't able to grasp from the documentation in which scenario one would like to have installed in a django project.

With that being said, could someone please explain which problem - and in which scenario - this library aim to solve?

Thanks!

[juanjcardona13]

Hi Murilo,

I can share a real-world use case from my experience where django-currentuser becomes extremely useful.

In my project, there was a requirement for certain models to include audit fields like created_by and updated_by. Handling this manually can get very tedious, especially when model instances can be created or updated from many different places — like the Django admin, APIs, management commands, etc.

Instead of passing the user manually everywhere and cluttering the code, django-currentuser allows me to access the current user inside the model’s save method directly. This way, I can automatically set those audit fields without worrying about where or how the model was created.

Additionally, writing all this logic manually would be verbose and error-prone. Having a middleware that tracks the current user globally and lets you fetch it easily from anywhere (models, signals, services) makes the development much cleaner and more maintainable.

In short, this library solves the problem of associating the logged-in user with database operations transparently and consistently across the entire Django application.

Hope this helps!