# Remove Django Permissions Default

**URL:** <https://forum.djangoproject.com/t/remove-django-permissions-default/31459>\
**Category:** Using the ORM\
**Created:** [May 23, 2024, 3:08pm UTC](https://forum.djangoproject.com/t/remove-django-permissions-default/31459 "2024-05-23T15:08:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [May 25, 2024, 1:45am UTC](https://forum.djangoproject.com/t/remove-django-permissions-default/31459/4 "2024-05-25T01:45:39Z")

</div>

It appears you might have an incomplete understanding of how the current permissions system works and how it’s intended to be used.

Permissions aren’t _tied_ to models. Yes, permissions are associated with models, but that’s _primarily_ for the benefit of the admin app. You are free to use permissions as you see fit.

Read the _complete_ threads at [Conditional content rendering, based on permissions](https://forum.djangoproject.com/t/conditional-content-rendering-based-on-permissions/21865) for a perspective on this.

Your views _check_ what permissions are granted to the user, the permissions aren’t “associated” with the view. (In most cases, a user is going to need to use more than one view - you may, or may not, want to use the same permission to grant access to more than one view.)

The Django permission system can effectively be used as the foundation of a “Role-based” access system, where the Group model is used for the roles, and the permissions granted to those groups identify what actions the members of that group can perform.

---

_[View the full topic](https://forum.djangoproject.com/t/remove-django-permissions-default/31459)._
