Skip to content

Configuration

Field History has no settings form. What a user sees is controlled by permissions, entity access and field access.

Supported entity types

Every revisionable content entity type with a Revisions page (a version-history link template) gets a Field History tab. In core, these are:

Entity type Field History page Revision access core requires
Content (node) /node/{nid}/field_history View all revisions, {Content type}: View revisions or Administer content
Media /media/{mid}/field_history View all media revisions or {Media type}: View any media revision pages
Taxonomy term /taxonomy/term/{tid}/field_history View all term revisions or {Vocabulary}: View term revisions
Content block /admin/content/block/{id}/field_history {Block type}: View content block history pages

Contributed entity types get a tab when they define a version-history link template.

Permissions

Grant these at Administration » People » Permissions.

Permission Machine name Needed for
View {entity type} field history view {entity_type} field history, for example view node field history The Field History tab on that entity type. Marked as restricted, because it reveals past field values.
The entity type's revision access See the table above Reading past revisions. Field History asks the entity's access handler for the view all revisions operation, the check core's Revisions page uses.

A user needs both. The field history permission alone does not reveal revisions.

For nodes, Bypass content access control alone is not enough, because core does not apply it to revision operations.

Entity access

The user must also be able to view the entity itself. On an unpublished node, the tab appears only for users who can see unpublished content, such as its author with View own unpublished content. Node access modules apply as they do for viewing the node.

Field access

Fields the user cannot view are left out of the overview, and their per-field pages return 403. Field access is checked on the current revision of the entity.