Template permission checks in Django - Step-by-Step Execution

Concept Flow - Template permission checks

User Request

↓

View Fetches User

↓

View Passes User to Template

↓

Template Receives User

↓

Template Checks Permissions

↓

Has Permission

↓

Show Content

The flow shows how a Django template receives a user object and checks permissions to decide what content to show.

Execution Sample

Django

{% if user.has_perm 'app.view_item' %}
  <p>Secret content here</p>
{% else %}
  <p>Access denied</p>
{% endif %}

This template code checks if the user has a specific permission and shows content accordingly.

Execution Table

Step	Template Line	Condition Checked	Result	Content Rendered
1	{% if user.has_perm 'app.view_item' %}	user.has_perm('app.view_item')	True	<p>Secret content here</p>
2	{% else %}	N/A	Skipped	N/A
3	{% endif %}	N/A	End if	N/A
4	Render complete	N/A	N/A	Secret content shown

💡 Permission check passed, so secret content is rendered and else block skipped.

Variable Tracker

Variable	Start	After Step 1	Final
user.has_perm('app.view_item')	Unknown	True	True

Key Moments - 2 Insights

Why does the template use user.has_perm instead of checking permissions in the view?

The template can directly check permissions to decide what to show, making the UI responsive to user rights without extra view logic. See execution_table step 1 where the condition is evaluated.

What happens if the user does not have the permission?

The else block runs, showing alternative content. This is shown in execution_table step 2 where else is skipped if permission is true, but would run if false.

Visual Quiz - 3 Questions

Look at the execution table, what content is rendered when user.has_perm returns True?

A <p>Access denied</p>

B <p>Secret content here</p>

C Nothing is rendered

D Both contents are rendered

💡 Hint

Check execution_table row 1 under Content Rendered.

At which step does the template decide to skip the else block?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at execution_table step 2 where else is marked as skipped.

If user.has_perm returned False, what would change in the execution table?

A No content would be rendered

B Step 1 result would be True and secret content rendered

C Step 1 result would be False and else block content rendered

D Template would error out

💡 Hint

Refer to variable_tracker and execution_table step 1 and 2 for permission check results.

Concept Snapshot

Django templates can check user permissions using {% if user.has_perm 'app.permission' %}.
If True, show protected content.
Else, show alternative or nothing.
This keeps permission logic simple and UI responsive.
Always pass user to template context.

Full Transcript

In Django, templates can check user permissions directly using the user.has_perm method. When a view passes the user object to the template, the template uses an if statement to check if the user has a specific permission. If the permission check returns true, the template renders the protected content. Otherwise, it renders an alternative message or hides the content. This approach allows the UI to adapt based on user rights without extra logic in the view. The execution table shows the step-by-step evaluation of the permission check and which content is rendered. The variable tracker follows the permission check result. Key moments clarify why permission checks happen in the template and what happens when permissions are missing. The visual quiz tests understanding of the permission check flow and rendering decisions.