---
title: "Provisioning Source Views for Trigger Events"
slug: "provisioning-source-views-for-trigger-events-tg"
tags: ["5.4"]
updated: 2026-10-28T01:54:14Z
published: 2026-10-28T01:54:14Z
canonical: "docs.vastdata.com/provisioning-source-views-for-trigger-events-tg"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Provisioning Source Views for Trigger Events

DataEngine triggers may be *element* type triggers, which watch for events related to elements in a *source view*. This includes creation and deletion of S3 objects or S3 object tags. In order that DataEngine users can create element triggers, a source view must be created to host those trigger events and it must be accessible to DataEngine users.

Application users cannot create source views. This must be done in VMS by a manager user (a *tenant admin* or *cluster admin* user).

To provide a source view, [create a view](/docs-5-4/docs/managing-views-tg) with the following configuration:

| VAST Web UI Field Name | Requirement |
| --- | --- |
| Path | Specify the path in the tenant's Element Store. |
| Create directory | Enable this. |
| Policy name | Select a view policy on the same tenant with *S3 Native* security flavor. To ensure that all *application users* can access the bucket, add the same user group that you are using to provision application users to the S3 *bucket listing permission* field in the policy configuration. |
| Protocols | Set this to S3 Bucket. |
| S3 bucket name | Enter a name for the bucket. |
| Bucket Owner | Provide the user you created in [Enabling Data Engine on a VAST Cluster Tenant](/docs-5-4/docs/en/enabling-data-engine-on-a-vast-cluster-tenant-tg). Click to enter the name and start typing and then select a name from the list. |

You can create and otherwise manage these views as described in [Managing Views](/docs-5-4/docs/managing-views-tg).