Determining entity create access¶

Available since: 1.1.0

Provided tokens

Token	Description
`[event]`	The event.
`[event:context]`	Contains a list of properties depending on the context of the event.
`[event:entity_bundle]`	The bundle of the entity.
`[event:uid]`	The ID of the user account of the event.
`[event]`	The event.
`[event:machine_name]`	The machine name of the ECA event.
`[session_user]`	The user account that dispatched the event, regardless if ECA is processing models under a different account. This is only available if ECA is configured to always run under a specific account.
`[account]`	The user account of the event.

Fires when Drupal checks whether a user can create a new entity of a given type and bundle. This wraps Drupal's hook_entity_create_access().

Use the Set access result action to grant or deny access.

No entity available

Since the entity does not exist yet, the [entity] token is not available in this event. You only have access to the entity type, bundle, language, and the requesting account via [account].

Fields¶

For any successor of this event, the account that asks for access is available under the [account] token. Example: [account:uid] provides the user ID of the account.

Furthermore, following data of the event is available:<ul><li>[event:operation] holds the requested operation, such as "view".</li></ul>

Restrict by entity type ID

Example: node, taxonomy_term, user

Restricts to the specified entity type (e.g., node, taxonomy_term). Comma-separated for multiple values.

Restrict by entity bundle

Example: article, tags

Restricts to the specified bundle (e.g., article, tags). For entities without bundles (like users), the bundle equals the entity type.

Restrict by language code

Example: en

Restricts to the specified language code (e.g., en). Useful in multilingual sites where create access might differ per language. Comma-separated for multiple values.