Wagtail adapts and extends the Django permission system to cater to the needs of website content creation, such as moderation workflows, and multiple teams working on different areas of a site (or multiple sites within the same Wagtail installation). Permissions can be configured through the ‘Groups’ area of the Wagtail admin interface, under ‘Settings’.


Whilst Wagtail supports a number of user roles and permissions, the Wagtail Admin should still be restricted to trusted users.

Page permissions

Permissions can be attached at any point in the page tree, and propagate down the tree. For example, if a site had the page tree:

    About us

then a group with ‘edit’ permissions on the ‘Offices’ page would automatically receive the ability to edit the ‘UK’, ‘France’, and ‘Germany’ pages. Permissions can be set globally for the entire tree by assigning them on the ‘root’ page - since all pages must exist underneath the root node, and the root cannot be deleted, this permission will cover all pages that exist now and in the future.

Whenever a user creates a page through the Wagtail admin, that user is designated as the owner of that page. Any user with ‘add’ permission has the ability to edit pages they own, as well as add new ones. This is in recognition of the fact that creating pages is typically an iterative process involving creating a number of draft versions - giving a user the ability to create a draft but not letting them subsequently edit it would not be very useful. The ability to edit a page also implies the ability to delete it; unlike Django’s standard permission model, there is no distinct ‘delete’ permission.

The full set of available permission types is as follows:

  • Add - grants the ability to create new subpages underneath this page (provided the page model permits this - see Parent page / subpage type rules), and to edit and delete pages owned by the current user. Published pages cannot be deleted unless the user also has ‘publish’ permission.

  • Edit - grants the ability to edit and delete this page, and any pages underneath it, regardless of ownership. A user with only ‘edit’ permission may not create new pages, only edit existing ones. Published pages cannot be deleted unless the user also has ‘publish’ permission.

  • Publish - grants the ability to publish and unpublish this page and/or its children. A user without publish permission cannot directly make changes that are visible to visitors of the website; instead, they must submit their changes for moderation. Publish permission is independent of edit permission; a user with only publish permission will not be able to make any edits of their own.

  • Bulk delete - allows a user to delete pages that have descendants, in a single operation. Without this permission, a user has to delete the descendant pages individually before deleting the parent. This is a safeguard against accidental deletion. This permission must be used in conjunction with ‘add’ / ‘edit’ permission, as it does not provide any deletion rights of its own; it only provides a ‘shortcut’ for the permissions the user has already. For example, a user with just ‘add’ and ‘bulk delete’ permissions will only be able to bulk-delete if all the affected pages are owned by that user, and are unpublished.

  • Lock - grants the ability to lock or unlock this page (and any pages underneath it) for editing, preventing users from making any further edits to it.

Drafts can be viewed only if the user has either Edit or Publish permission.

Image / document permissions

The permission rules for images and documents work on a similar basis to pages. Images and documents are considered to be ‘owned’ by the user who uploaded them; a user with ‘add’ permission also has the ability to edit items they own; and deletion is considered equivalent to editing rather than having a specific permission type.

Access to specific sets of images and documents can be controlled by setting up collections. By default, all images and documents belong to the ‘root’ collection, but users with appropriate permissions can create new collections in the Settings -> Collections area of the admin interface. Permissions set on ‘root’ apply to all collections, so a user with ‘edit’ permission for images in the root collection can edit all images; permissions set on other collections only apply to that collection and any of its sub-collections.

The ‘choose’ permission for images and documents determines which collections are visible within the chooser interface used to select images and document links for insertion into pages (and other models, such as snippets). Typically, all users are granted choose permission for all collections, allowing them to use any uploaded image or document on pages they create, but this permission can be limited to allow creating collections that are only visible to specific groups.

Collection management permissions

Permission for managing collections themselves can be attached at any point in the collection tree. The available collection management permissions are as follows:

  • Add - grants the ability to create new collections underneath this collection.

  • Edit - grants the ability to edit the name of the collection, change its location in the collection tree, and change the privacy settings for documents within this collection.

  • Delete - grants the ability to delete collections that were added below this collection. Note: A collection must have no subcollections under it and the collection itself must be empty before it can be deleted.


Users are not allowed to move or delete the collection that is used to assign them permission to manage collections.

Adding custom permissions

See Django’s documentation on custom permissions for details on how to set permissions up.

Added in version 6.1: The ability to have custom permissions with codenames starting with add_, change_, or delete_ was added.

Permissions for models registered with Wagtail will automatically show up in the Wagtail admin Group edit form. For other models, you can also add the permissions using the register_permissions hook (see register_permissions).

To add a custom permission to be used in the Wagtail admin without relating to a specific model, you can create it using the content type of the wagtail.admin.models.Admin model. For example:

from django.contrib.auth.models import Permission
from django.contrib.contenttypes.models import ContentType
from wagtail.admin.models import Admin

content_type = ContentType.objects.get_for_model(Admin)
permission = Permission.objects.create(
    name="Can do something",

After registering the permission using the register_permissions hook, it will be displayed in the Wagtail admin Group edit form under the ‘Other permissions’ section, alongside the ‘Can access Wagtail admin’ permission.

Added in version 6.1: The ability to register custom permissions in the “Other permissions” section was added.

FieldPanel and PanelGroup permissions

Permissions can be used to restrict access to fields within the editor interface. See permission on FieldPanel.

Permissions can be used to restrict groups of panels via the permission keyword argument on PanelGroup classes (TabbedInterface, ObjectList, FieldRowPanel, MultiFieldPanel). See how PanelGroup usage can be customized Panels.