Object-level permissions concept in Django - Mini Project: Build & Apply

Object-level permissions concept in Django

📖 Scenario: You are building a Django app where users can create and manage their own blog posts. You want to make sure that only the author of a post can edit or delete it. This is called object-level permission.

🎯 Goal: Build a simple Django model for blog posts and add a method to check if a user has permission to edit the post based on whether they are the author.

📋 What You'll Learn

Create a Django model called Post with fields title, content, and author (ForeignKey to User)

Add a boolean method can_edit(self, user) to Post that returns True if user is the author

Create a sample Post instance with a specific author

Check the permission method with a user instance

💡 Why This Matters

🌍 Real World

Object-level permissions are used in apps where users own data and should only modify their own content, like blogs, social media, or project management tools.

💼 Career

Understanding object-level permissions is important for backend developers to secure user data and implement proper access control in web applications.

1

Create the Post model

Create a Django model called Post with fields: title as a CharField with max length 100, content as a TextField, and author as a ForeignKey to User with on_delete=models.CASCADE.

Django

from django.db import models
from django.contrib.auth.models import User

# Define the Post model here

Hint

Use models.CharField for title, models.TextField for content, and models.ForeignKey for author linking to User.

2

Add the permission method

Inside the Post model, add a method called can_edit(self, user) that returns True if the user is the same as the author of the post, otherwise False.

Django

from django.db import models
from django.contrib.auth.models import User

class Post(models.Model):
    title = models.CharField(max_length=100)
    content = models.TextField()
    author = models.ForeignKey(User, on_delete=models.CASCADE)

    # Add can_edit method here

Hint

The method compares the user argument with self.author and returns the result.

3

Create a sample Post instance

Create a variable called author_user as an instance of User with username 'alice'. Then create a Post instance called post with title 'My First Post', content 'Hello world!', and author set to author_user.

Django

from django.db import models
from django.contrib.auth.models import User

class Post(models.Model):
    title = models.CharField(max_length=100)
    content = models.TextField()
    author = models.ForeignKey(User, on_delete=models.CASCADE)

    def can_edit(self, user):
        return user == self.author

# Create author_user and post instances here

Hint

Create author_user with username 'alice' and then create post using that user as author.

4

Check edit permission for a user

Create a variable called can_edit_post that stores the result of calling post.can_edit(author_user) to check if author_user can edit the post.

Django

from django.db import models
from django.contrib.auth.models import User

class Post(models.Model):
    title = models.CharField(max_length=100)
    content = models.TextField()
    author = models.ForeignKey(User, on_delete=models.CASCADE)

    def can_edit(self, user):
        return user == self.author

author_user = User(username='alice')
post = Post(title='My First Post', content='Hello world!', author=author_user)

# Check if author_user can edit the post

Hint

Call the can_edit method on post passing author_user and assign the result to can_edit_post.

Practice

1. What is the main purpose of object-level permissions in Django?

easy

A. To speed up database queries

B. To manage user passwords securely

C. To create new database tables automatically

D. To control access to individual data items or objects

Solution

1. Step 1: Understand what object-level permissions mean

   Object-level permissions allow control over access to specific individual objects, not just general models.

2. Step 2: Compare with other options

   Options A, B, and D relate to security, performance, or database structure, not object-level access control.

3. Final Answer:

   To control access to individual data items or objects -> Option D

4. Quick Check:

   Object-level permissions = control individual objects [OK]

Hint: Object-level means per item, not general model access [OK]

Common Mistakes:

• Confusing object-level with model-level permissions
• Thinking it manages passwords or database structure
• Assuming it improves query speed

2. Which of the following is the correct way to check object-level permission for a user in Django using django-guardian?

easy

A. user.has_perm('app.view_model', obj)

B. user.has_perm('app.view_model')

C. user.check_perm('app.view_model', obj)

D. user.can_access('app.view_model', obj)

Solution

1. Step 1: Recall django-guardian permission check syntax

   django-guardian extends Django's has_perm method to accept an object as a second argument for object-level checks.

2. Step 2: Analyze options

   user.has_perm('app.view_model', obj) uses has_perm with object, which is correct. user.has_perm('app.view_model') lacks object, so it's model-level. Options C and D use incorrect method names.

3. Final Answer:

   user.has_perm('app.view_model', obj) -> Option A

4. Quick Check:

   has_perm with object = correct syntax [OK]

Hint: Use has_perm with object argument for object-level checks [OK]

Common Mistakes:

• Omitting the object argument in has_perm
• Using non-existent methods like check_perm or can_access
• Confusing model-level and object-level permission checks

3. Given the code snippet:

from guardian.shortcuts import assign_perm
assign_perm('change_article', user, article)

if user.has_perm('change_article', article):
    print('Can edit')
else:
    print('Cannot edit')

What will be printed if the permission was assigned correctly?

medium

A. Cannot edit

B. Can edit

C. PermissionError

D. No output

Solution

1. Step 1: Understand permission assignment

   The assign_perm function assigns the 'change_article' permission to the user for the specific article object.

2. Step 2: Check permission with has_perm

   The user.has_perm('change_article', article) call returns True because the permission was assigned.

3. Final Answer:

   Can edit -> Option B

4. Quick Check:

   Assigned permission means has_perm returns True [OK]

Hint: Assign permission then has_perm returns True for that object [OK]

Common Mistakes:

• Assuming has_perm returns False without model-level permission
• Expecting exceptions instead of boolean
• Confusing permission names or forgetting object argument

4. Identify the error in this code snippet for checking object-level permission:

if user.has_perm('delete_post'):
    print('Can delete')
else:
    print('Cannot delete')

Assuming you want to check permission on a specific post object.

medium

A. Missing the object argument in has_perm method

B. Using wrong permission name 'delete_post'

C. Should use user.check_perm instead of has_perm

D. No error, code is correct

Solution

1. Step 1: Understand object-level permission check

   To check permission on a specific object, has_perm must include the object as the second argument.

2. Step 2: Analyze the code

   The code calls has_perm without the object, so it checks model-level permission only, not object-level.

3. Final Answer:

   Missing the object argument in has_perm method -> Option A

4. Quick Check:

   Object-level check needs object argument [OK]

Hint: Always pass object to has_perm for object-level checks [OK]

Common Mistakes:

• Forgetting the object argument in has_perm
• Using incorrect method names
• Assuming model-level permission covers object-level

5. You want to allow users to edit only the articles they own. Which approach correctly applies object-level permissions in Django?

hard

A. Use Django's default group permissions without object checks

B. Grant all users the 'change_article' permission globally on the Article model

C. Assign 'change_article' permission to each user only for their own article objects using django-guardian

D. Override the Article model's save method to check user ownership

Solution

1. Step 1: Understand the requirement

   Users should edit only their own articles, so permission must be specific to each article object.

2. Step 2: Evaluate options

   Assign 'change_article' permission to each user only for their own article objects using django-guardian assigns permission per object, matching the requirement. Grant all users the 'change_article' permission globally on the Article model grants global permission, allowing edits on all articles. Use Django's default group permissions without object checks ignores object-level control. Override the Article model's save method to check user ownership is unrelated to permissions.

3. Final Answer:

   Assign 'change_article' permission to each user only for their own article objects using django-guardian -> Option C

4. Quick Check:

   Object-level permission per user per object = Assign 'change_article' permission to each user only for their own article objects using django-guardian [OK]

Hint: Assign permissions per object to enforce ownership editing [OK]

Common Mistakes:

• Granting global permissions instead of per-object
• Ignoring object-level permission packages like django-guardian
• Trying to enforce ownership via model save method