{"id":7818,"date":"2019-08-30T12:54:48","date_gmt":"2019-08-30T12:54:48","guid":{"rendered":"https:\/\/www.botreetechnologies.com\/blog\/?p=7818"},"modified":"2026-04-01T12:20:09","modified_gmt":"2026-04-01T06:50:09","slug":"django-user-groups-and-permission","status":"publish","type":"post","link":"https:\/\/www.botreetechnologies.com\/blog\/django-user-groups-and-permission\/","title":{"rendered":"Django User Groups and Permission"},"content":{"rendered":"\n

We had a content curation application covering 4 roles Admin, Editor, Contributor, and Client.<\/p>\n\n\n\n

Each of the roles had certain permission and access rights, and we had to block access to unauthorized roles. This would have been simple if the access had been at model level but we had to give them access at the object level.<\/p>\n\n\n\n

For example let us say there were 2 editors editor A and editor B if editor A has created a content X then editor B should not be able to view, edit or delete content X unless he has been assigned to the content X.<\/p>\n\n\n

\n
\"Call<\/a><\/figure>\n<\/div>\n\n\n

Django<\/a> does provide groups and permissions option but this is a model or table level and not at the object level. Hence we decided on creating groups based on the objects on which we want to provide the access and the users were added to these groups as per requirement or based on the existing state of an object.<\/p>\n\n\n\n

So our solution had 3 parts,<\/p>\n\n\n\n