> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/review-events-and-save-evidence/events/event-flow.md). # Event Flow Learn how to use Solink's Event Flow feature and create a process for reviewing notable events. **Event Flow** allows you to **review** and **tag** events by answering a set of configurable questions. {% embed url="" %} Event Flow is a helpful tool for quickly reviewing and tagging events, allowing you or another Solink user to revisit the event later. Event Flow can help you properly categorize: * Suspicious transactions * Theft * Training opportunities (saving the event to use in training content) *** ## Event Flow Setup To create a new Event Flow, you must be an **Admin** user OR have the following [User permissions](/docs/manage-users-locations-and-your-account/users-page.md) (located **Settings** > **User Roles** page > **Edit** a user > **User Permissions** > **Events** section): * **Event Flow Response** must be set to "On" * **Manage Event Workflows** must be set to "On" **Note**: Users must have both of the permissions outlined above enabled to review events and see Event Flow results. Users who do not have these permissions will not be able to review or see results. To navigate to the **Event Flow** setup page: 1. Select Solink **Settings** (select your username in the top-right corner > **Settings**) 2. Select the **Event Flow** tab: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-a9b69555545ce31f0b15461defc87567b1952a84%2F6b8cfb051d194e6f.png?alt=media) 3\. Select **+New** to begin creating a new Event Flow: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-989a77cee6614592c86b3be900e635928d57f166%2Ff8cd967138070d97.png?alt=media) ### Create Yes/No Workflow On the **Create Workflow** page, you can create a new Event Workflow starting with a simple "Yes" or "No" question: Additionally, you can decide whether to \[create follow\\-up questions]\(#create-follow-up-questions-and-reponses-optional) with their own set of custom responses when the user responds to either of the "Yes" or "No" questions. Follow these steps to create a Yes/No workflow: 1. Type a name for the workflow. This allows you to locate the workflow from the main **Event Flow** page in **Settings** later (if you need to review, edit or delete the workflow). 2. Select the **Event Type** to apply this workflow to. For example, if you select **Transaction**, your workflow will appear on all transaction events. **Note**: There is a limit of one event flow per event type. 3. Input a Yes or No question. For example, you may want to ask "Does this transaction require attention?" and then create follow-up questions and/or responses based on the Yes/No answer to this question: Select **Save** to apply the workflow to your selected event type: This is what the workflow will look like whenever you or another user reviews a transaction event: You can also create additional follow-up questions and responses to each of the initial Yes and No responses. Creating further questions and responses can help users drill down to a specific answer when reviewing events and provide more accurate tagging. See the next section below for more information on creating follow-up questions and responses. ### Create Follow-Up Questions and Reponses (Optional) Select one of the **Follow-Up Question** checkboxes (for either a Yes or No response) to begin creating follow-up questions and responses: 1. Type the follow-up question in the **Question** field. In this example, the user will be prompted with a follow-up question when the user selects "Yes" in response to the initial question: 2. Type a minimum of **two** responses to the follow-up question: This is what the workflow will look like whenever you or another user reviews a transaction event: (Optional) Select the **Add Response** button to add an additional response to the follow-up question. There is a limit of 10 responses per follow-up question: (Optional) You can also create a further follow-up question and set of responses, if necessary. For example, if you want the user to be prompted with another question and set of responses after they select "Suspicious transaction, requires further review", select the **Follow-Up Question** checkbox and create the follow-up question and responses: ### Edit/Delete Existing Event Flows To **edit** or **delete** existing event flows, navigate to Solink Settings > Event Flow page: **Note**: You cannot recover your Event Flow once deleted. *** ## How to Review Events {% tabs %} {% tab title="Web" %} Users can review events configured in Event Flow from the **Events** page. 1. Select the **Review** button within the event card to proceed through the Event Flow: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-540ec1b297da2a84700304e73b92bfbbb43e24ad%2F0f8164e560bc943b.png?alt=media) 2. Users can respond either with **Yes** or **No** to the Event Flow question: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-6e00a0fcd10cf5b4c6af3f1bb903a786ba8901b0%2F4b7cfbc14b178a5b.png?alt=media) If there are additional questions, simply follow the Event Flow and answer the questions until finished. The event is tagged so it can be reviewed later. {% endtab %} {% tab title="Mobile" %} You can review events configured in Event Flow in the Solink mobile app. You cannot review alarm events with Event Flow. To review an event: 1. On the **Events** page, open the event. 2. Tap **Review** in the toolbar under the video.
3. Tap an answer to each question until the Event Flow is finished. To go back to the previous question, tap the back arrow. When you finish, the app shows who reviewed the event and when. The **Review** button shows an outline for events that are already reviewed. Tap it to see the result. **Note:** Some question types are not available in the mobile app yet. If the app shows that a question type is not supported, use the Solink web platform to review the event. To undo a reviewed event, also use the web platform. {% endtab %} {% endtabs %} ### Undo Reviewed Event You can "undo" an Event Flow after a user has reviewed it. This allows a user to reset the flow and respond to the questions once again. To undo: 1. Select the **See Verification Result** button. 2. Select the "X" icon on the recorded response to reset the Event Flow. ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-7e7d68da018f4850dfc32ff8f30cd945707fb6f8%2F7646883b251822b3.png?alt=media) *** ## See Event Flow History (Audit Logs) You can review event **audit logs** to see which user reviewed the event and what their response was. Select the **See Verification Result** button (only displays if a user has reviewed the event): ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-d0f4626fd1564d44e6d545524aa808d3d42b3fd4%2Feb5dbcb4344b8396.png?alt=media) Next, select the **Audit Log** button. The Audit Log displays the response the user chose, the name of the user (email), and the date and time the user responded: *** ## Find Tagged Events You can use the filters on the **Events** page to locate events tagged with a specific answer. To locate a tagged event: 1. Select **Add Filter**. 2. Select **Filter Categories**. 3. Select **Event Flow**. ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-6242d07309e2e1c5882b3157850be87b03abd0e9%2F8ec382b8180b872e.png?alt=media) From here, you can filter by the following: * **Event Flow Conclusion**: Filter all of your tagged events by either **Yes** or **No** responses to the initial question: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-3ceac2b5f15843c4ce0ca1c5c7f1d019c4a66ca6%2F774bf9656a81352d.png?alt=media) * **Event Flow Responses**: Filter all of your tagged events by the response(s) to your follow-up Event Flow questions: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-0fbe914dbb936cdedb81210b6a387b76d6f95b1e%2Ffaa10b4324ff6800.png?alt=media) *** ## Event Flow Examples Below are some examples you may want to replicate when creating an Event Flow to get the most value out of this feature. It is also best practice to simply ask "Has this event been reviewed?" for any event type, as this ensures you are able to tag "No" events for review later. ### Transaction Event Flow Example Follow the Event Flow structure pictured below to create a helpful transaction workflow: ### Blocked Exit Event Flow Example Follow the Event Flow structure pictured below to create a helpful [blocked exit](/docs/understand-your-business/ai-features/compliance-analytics/blocked-exit-detection.md) workflow (no follow-up questions required): *** ## Event Flow FAQs Below are a list of frequently asked questions for the Event Flow feature. ### What user permissions are required to respond to and create event flows? The following permissions are required for Event Flow: * **Event Flow Response**: Enable this permission for a user to allow the user to review/respond to Event Flows. * **Manage Event Workflows**: Enable this permission for a user to allow the user to create new and edit existing Event Flows. See [Event Flow Setup](#event-flow-setup) for more information. ### Can multiple users work on the same Event Flow? Can one person start responding to a Event Flow while another completes it? No, one user must fully respond to the Event Flow in order to be logged— progress is not saved until the Event Flow has been fully responded to. ### Can I Edit Event Flow Questions? Yes, you must have the **Manage Event Workflows** permission enabled ([see above](#what-user-permissions-are-required-to-respond-to-and-create-event-flows)). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/review-events-and-save-evidence/events/event-flow.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.