Skip to main content
Alongside the workflows scoped to human accounts, non-human identities, and secrets, Oleria has five templates that automate other recurring Security and Workspace tasks. Select Manage on a template to see instances already built from it, or Create to configure a new one. See How workflows work for the Trigger/Condition/Approval/Action structure every workflow shares - not every template below uses all four.

Activity alert

Unlike the other templates on this page, this one isn’t schedule-based - it runs automatically whenever Oleria ingests new activity matching the filters you set.
This workflow template must be enabled for your workspace - contact support@oleria.com if you don’t see Activity alert in Workflow templates.
1

Trigger

This workflow has no schedule. It runs when Activity Analysis receives new activity, and only emails you about activity it hasn’t already reported.
2

Choose filters

Set the filters that decide which activity triggers an alert, using the same fields available in Activity analysis - for example Application includes GCP and Activity Type includes secret.added. You’ll be emailed when new activity matching these filters appears. Activity from before you save the workflow isn’t included.
3

Notify

Add Recipients with administrator access to Oleria. Oleria emails them as soon as a match appears.
Select Create alert directly on Activity analysis to build one from the table’s current filters, instead of starting from the template.

Enforce MFA compliance

Runs on a schedule, escalates non-compliant accounts, and notifies you once that happens.
1

Trigger

Set a schedule for the workflow to run: Frequency (Daily, Weekly, or Monthly), the Day of Week or Day of the Month, and the time to Execute At.
2

Filter Records

Choose the scope of applications for MFA enforcement - across all application instances, or specific ones you select. External and disabled users are excluded.
3

Escalation

Set the reviewer role (Manager) and an Alternate reviewer, notified if the user’s manager isn’t configured, plus Expire review after - the deadline by which MFA must be configured. After that deadline passes, a notification goes to the escalated reviewers.
4

Notifications

Oleria always emails non-compliant users when a violation is detected, and can also notify by Slack or Microsoft Teams.

Manage stale SharePoint sites

Runs on a schedule, finding SharePoint sites that have gone dormant, and routes each one for a decision.
Requires a SharePoint integration. Without one connected, the template shows SharePoint integration required instead of letting you build a workflow from it.
1

Trigger

Set a schedule for the workflow to run: Frequency (Daily, Weekly, or Monthly), the Day of Week or Day of the Month, and the time to Execute At.
2

Find sites

Define the fields that identify dormant sites: Dormant Days, and optionally Data classification.
3

Approvals

Set the Approver to Site owners and choose an Alternate approver.
4

Actions

On this step, choose what Manage site access does once approved - Notify only (the default) or Remove all access - and set the Actions on incomplete approval requests: Do not take action, or Automatically take specified action.
Select View all approval logs from the build details panel to see every approval a workflow has generated.

Detect and report Shadow IT

Runs on a schedule, opening an incident ticket for each new shadow application found since the last run.
Oleria allows one Shadow IT workflow per workspace. Once you’ve built one, the template shows as Already configured instead of letting you create another.
1

Trigger

Set a schedule for the workflow to run: Frequency (Daily, Weekly, or Monthly), the Day of Week or Day of the Month, and the time to Execute At.
2

Filter Records

Oleria selects Shadow IT apps discovered through your connected OAuth integrations. Turn on Also include apps already in your inventory to also create tickets for shadow apps detected before the workflow started. With it off, the first run creates no tickets.
3

Configuration

The Destination System shown is your connected ITSM tool, such as Jira - it’s read-only, since Oleria creates tickets in whichever ITSM tool your workspace has connected. The Project, Issue Type, and Reporter shown below it are also read-only - Oleria pulls them from that system’s ticketing configuration rather than letting you set them on this template.
4

Notifications

Under Recipients, each connected identity provider instance is listed with a Select Admins picker. Choose at least one of that instance’s administrators for each instance that has any. Then turn on Send email notification, and if you also want a messaging alert, turn on Send Slack notification or Send Microsoft Teams notification - only the one your workspace has connected appears, since you can only connect one messaging channel at a time. Email can run alongside it.

Security insights email

Runs on a schedule, emailing a saved view’s results to the recipients you configure.
1

Trigger

Set a schedule for the workflow to run: Frequency (Daily, Weekly, or Monthly), the Day of Week or Day of the Month, and the time to Execute At.
2

Filter Records

Search for and apply one of your saved Views by name. Applying it carries over that view’s own record type and filters - there’s no separate filter builder in this step, so build the view first if you need one.
3

Actions

Add Recipients. Oleria sends them a Send Security Insights Email message with the records found based on the view’s criteria - so stakeholders get a recurring report without anyone pulling the data by hand.

Reviewing runs

Every template’s instances have a Runs tab showing their execution history - when each one ran, what it found, and what it did as a result.

Contact us

For questions, contact us at support@oleria.com.