Djangocms_reversion2 doesn’t introduce new permissions. It makes use of the page permissions of djangocms.

Activate djangocms page permissions: You have to add CMS_PERMISSIONS = True to your!

The natural intuition is: A person that can edit a page can also edit PageVersions and so on.

Integration with djangocms-moderation

This plugin replaces the “publish button” with a “moderation request button”. Then a “moderation workflow” is attached to the page. Now the edit functions of the page are blocked until the workflow is either rejected or approved.

How we could use this:

  1. We still hide the toolbar in the “edit page version” mode but add another button that triggers a special workflow
  2. When that workflow has finished
  3. Here comes the tricky part with djangocms-moderation -> they are building a workflow for approval of page publishing
    -> we would like to use this in future releases. This might look like this:
    • the external starts a new moderation request on the edited hidden_page
    • we use @receiver(post_obj_operation) signal handler to catch the end of the workflow
    • instead of clicking the publish button on the hidden_page (we make a rollback of the connected draft)

Implementation of the current permission system

We make use of the cms page permissions because they are already there and we don’t get any inconsistencies with custom permissions. Every page has a pagepermission_set. If a new page version is created all of these permissions have to be copied to the hidden_page of the page version. But there are also permissions that can be inherited from parent.

Therefore we use utils.inherited_permissions(page) to obtain all relevant inherited page permissions, then we have to transform them a little bit. I am talking about the following to cases where the permission is explicitly set to only affect the children or descendants.

We change the grant_on attribute of the copied permission in the left case to the right value:


As a consequence, if you make changes to the permissions of your original page they will currently not be applied to the page versions. Example: The permissions of a page are removed for a person. That person could still access the PageVersions of the past.


If a user can view a page she or he can view its page versions.


A user can create a page version for pages for which he has the An admin can create a page if he has cms.page_global_permission.can_change_page_global_permission

cms.utils.page_permissions: user_can_change_page


Only superusers are allowed to use the batch creation.


A user can edit page versions of pages that he is allowed to edit. TODO: see copy pagepermissions on copy (see


Attention: A user mustn’t delete own page versions because it might harm the page version tree. TODO: So far page versions cannot be deleted at all ;)

An admin can delete page versions if he has the cms.page_global_permission.can_delete_page_global_permission


A user can roll back a page to a page version if he has the permission to publish the page ( An admin can rollback a page if he has any global page permission (cms.page_global_permission.can_change_page_global_permission)

Example: How the check works

# check if the current user is allowed to revert the page by checking the publish permission
user = get_current_user()
if not user_can_publish_page(user, page_version.draft):
    messages.error(request, _('Missing permission to publish this page which is necessary for the rollback'))
    prev = request.META.get('HTTP_REFERER')
    if prev:
        return redirect(prev)
        raise Http404