DigitalDocumentPermissionType

DigitalDocumentPermissionType is a schema.org Enumeration for the access level granted on a DigitalDocument. It is the value of DigitalDocumentPermission.permissionType.

It has 3 members:

ReadPermission: can view but not modify or comment.
CommentPermission: can view and comment but not modify.
WritePermission: can modify (implicitly can also read and comment).

Full example of schema.org/DigitalDocumentPermissionType json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/DigitalDocumentPermissionType

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DigitalDocument",
  "name": "Xoo Code weekly sync — 2026-04-15",
  "hasDigitalDocumentPermission": [
    { "@type": "DigitalDocumentPermission", "permissionType": "https://schema.org/WritePermission", "grantee": { "@type": "Organization", "name": "Xoo Code core team" } },
    { "@type": "DigitalDocumentPermission", "permissionType": "https://schema.org/CommentPermission", "grantee": { "@type": "Audience", "audienceType": "Xoo Code contractors" } },
    { "@type": "DigitalDocumentPermission", "permissionType": "https://schema.org/ReadPermission", "grantee": { "@type": "Audience", "audienceType": "Observers" } }
  ]
}
</script>

The DigitalDocumentPermission wrapper

Permissions on a DigitalDocument are modelled via hasDigitalDocumentPermission linking to one or more DigitalDocumentPermission entries, each pairing a permissionType (this enum) with a grantee (Person, Organization, Audience, or ContactPoint).

Minimal valid version

The smallest markup that still produces a valid DigitalDocumentPermissionType entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/DigitalDocumentPermissionType (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DigitalDocumentPermission",
  "permissionType": "https://schema.org/ReadPermission",
  "grantee": { "@type": "Organization", "name": "Xoo Code" }
}
</script>

Google rich results this unlocks

DigitalDocumentPermissionType is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). DigitalDocumentPermissionType becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common DigitalDocumentPermissionType mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

01
Free-text permission
Wrong
```
"permissionType": "edit"
```
Right
```
Enum URL
```
Permission levels carry consistent meaning only through the enum; free text is parsed loosely.

Schema properties in this example

DigitalDocumentPermissionType Enumeration ReadPermission CommentPermission WritePermission DigitalDocument hasDigitalDocumentPermission DigitalDocumentPermission permissionType grantee Person Organization Audience audienceType

About the example data

The Xoo Code team meeting notes with tiered access: WritePermission for core team, CommentPermission for contractors, ReadPermission for observers.

Comments

Loading comments...