Template-level authorization in Flask

Introduction

Template-level authorization helps control what parts of a web page a user can see based on their permissions. It keeps your app safe by hiding or showing content depending on who is logged in.

You want to show a special admin menu only to admin users.

You want to hide edit buttons from users who cannot change content.

You want to display different messages based on user roles.

You want to prevent unauthorized users from seeing sensitive data on a page.

Syntax

Flask

{% if condition %}
  <!-- content to show if condition is true -->
{% else %}
  <!-- content to show if condition is false -->
{% endif %}

Use Flask's current_user or your own user object to check permissions inside templates.

Conditions can check roles, permissions, or any user attribute.

Examples

Shows a welcome message if the user is logged in, otherwise asks to log in.

Flask

{% if current_user.is_authenticated %}
  <p>Welcome, {{ current_user.username }}!</p>
{% else %}
  <p>Please log in.</p>
{% endif %}

Shows an admin dashboard link only if the user has the 'admin' role.

Flask

{% if 'admin' in current_user.roles %}
  <a href="/admin">Admin Dashboard</a>
{% endif %}

Shows an edit button only if the user has permission to edit.

Flask

{% if current_user.can_edit %}
  <button>Edit Post</button>
{% else %}
  <p>You cannot edit this post.</p>
{% endif %}

Sample Program

This Flask app shows how to use template-level authorization. It displays a welcome message and an admin dashboard link only if the user is logged in and has the admin role.

Flask

from flask import Flask, render_template_string
from flask_login import LoginManager, UserMixin, login_user, current_user

app = Flask(__name__)
app.secret_key = 'secret'

login_manager = LoginManager(app)

class User(UserMixin):
    def __init__(self, id, username, roles):
        self.id = id
        self.username = username
        self.roles = roles

@login_manager.user_loader
def load_user(user_id):
    # For demo, return a user with admin role
    return User(user_id, 'Alice', ['admin'])

@app.route('/')
def home():
    template = '''
    {% if current_user.is_authenticated %}
      <p>Welcome, {{ current_user.username }}!</p>
      {% if 'admin' in current_user.roles %}
        <a href="/admin">Admin Dashboard</a>
      {% else %}
        <p>Standard user dashboard</p>
      {% endif %}
    {% else %}
      <p>Please log in.</p>
    {% endif %}
    '''
    return render_template_string(template)

with app.test_request_context():
    user = User('1', 'Alice', ['admin'])
    login_user(user)
    print(home())

Important Notes

Always check user permissions in both backend and templates for security.

Use Flask-Login's current_user to access user info in templates.

Keep template logic simple to avoid clutter and confusion.

Summary

Template-level authorization controls what users see based on their roles or permissions.

Use {% if %} blocks in templates to show or hide content.

Combine backend checks with template checks for better security.

Practice

1. What is the main purpose of using template-level authorization in a Flask application?

easy

A. To control what content users can see based on their roles or permissions

B. To speed up the loading time of templates

C. To change the style of the webpage dynamically

D. To store user data securely in the database

Solution

1. Step 1: Understand template-level authorization

   Template-level authorization is about controlling visibility of content in templates based on user roles or permissions.

2. Step 2: Identify the main purpose

   The main goal is to restrict or allow content display depending on who the user is.

3. Final Answer:

   To control what content users can see based on their roles or permissions -> Option A

4. Quick Check:

   Authorization controls content visibility [OK]

Hint: Authorization controls content visibility in templates [OK]

Common Mistakes:

• Confusing authorization with styling or performance
• Thinking it stores data instead of controlling view
• Mixing backend data storage with frontend display control

2. Which of the following is the correct way to check a user's role in a Flask Jinja2 template?

easy

A. {{ if user.role == 'admin' }} ... {{ endif }}

B. {% check user.role == 'admin' %} ... {% endcheck %}

C. {% if user.role == 'admin' %} ... {% endif %}

D. <% if user.role == 'admin' %> ... <% endif %>

Solution

1. Step 1: Recall Jinja2 syntax for conditionals

   Jinja2 uses {% if condition %} ... {% endif %} blocks for conditional rendering.

2. Step 2: Match syntax with options

   {% if user.role == 'admin' %} ... {% endif %} uses correct Jinja2 syntax. The other options use invalid or other template syntax.

3. Final Answer:

   {% if user.role == 'admin' %} ... {% endif %} -> Option C

4. Quick Check:

   Jinja2 uses {% if %} ... {% endif %} [OK]

Hint: Use {% if %} ... {% endif %} for conditions in Jinja2 templates [OK]

Common Mistakes:

• Using {{ }} for control flow instead of {% %}
• Confusing Jinja2 with other template languages
• Using incorrect tags like <% %> which are not Jinja2

3. Given this Flask template snippet:

{% if user.is_authenticated and user.role == 'editor' %}
  
Edit content here
{% else %}
  
View only
{% endif %}

What will be displayed if user.is_authenticated is True but user.role is 'viewer'?

medium

A. Edit content here

B. View only

C. Nothing will be displayed

D. Template error occurs

Solution

1. Step 1: Evaluate the condition

   The condition requires user.is_authenticated to be True AND user.role to be 'editor'. Here, role is 'viewer', so condition is False.

2. Step 2: Determine which block runs

   Since condition is False, the else block runs, displaying <p>View only</p>.

3. Final Answer:

   <p>View only</p> -> Option B

4. Quick Check:

   Condition false triggers else block [OK]

Hint: Check both conditions; else block shows if any fail [OK]

Common Mistakes:

• Assuming only one condition matters
• Thinking 'viewer' role passes the 'editor' check
• Expecting no output when else block exists

4. You have this template code:

{% if user.role = 'admin' %}
  
Admin panel
{% endif %}

What is the problem with this code?

medium

A. Using <p> tags inside a template is not allowed

B. Missing else block for non-admin users

C. Incorrect indentation inside the if block

D. Using single equals sign (=) instead of double equals (==) in the if condition

Solution

1. Step 1: Identify the conditional syntax error

   In Jinja2, comparisons use '==' not '='. '=' is assignment and invalid in if conditions.

2. Step 2: Understand the impact

   Using '=' causes a template syntax error and prevents rendering.

3. Final Answer:

   Using single equals sign (=) instead of double equals (==) in the if condition -> Option D

4. Quick Check:

   Use '==' for comparisons in Jinja2 if statements [OK]

Hint: Use '==' for comparisons, '=' causes errors [OK]

Common Mistakes:

• Using '=' instead of '==' in conditions
• Thinking missing else causes syntax error
• Believing HTML tags are disallowed in templates

5. You want to show a special admin menu only if the user is authenticated and has either 'admin' or 'superuser' role. Which template code correctly implements this?

hard

A. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %}
Admin Menu
{% endif %}

B. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

C. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
Admin Menu
{% endif %}

D. {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

Solution

1. Step 1: Understand the condition requirements

   User must be authenticated AND have role 'admin' OR 'superuser'.

2. Step 2: Analyze each option

   {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} lacks parentheses around the or conditions, resulting in incorrect logic: (is_authenticated and role=='admin') or role=='superuser' due to operator precedence. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} uses or between authentication and roles, allowing unauthenticated users. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
   Admin Menu
   {% endif %} has incorrect syntax and logic. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} uses 'in' to check role membership, which is clean and correct.

3. Final Answer:

   {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} -> Option A

4. Quick Check:

   Use 'in' for multiple role checks with and for authentication [OK]

Hint: Use 'and' plus 'in' to check multiple roles cleanly [OK]

Common Mistakes:

• Using 'or' instead of 'and' for authentication
• Incorrect syntax for multiple role checks
• Missing parentheses causing logic errors