Product area
Automation
Automations and the actions they run, by hand or when a policy finds a violation.
84 pages · All tags
Getting started 1
- Getting startedAfter your first scan
After the first scan, check the inventory, turn on a first set of policies, fix one violation and add a first automation and dashboard.
Guides 21
- Guides › AutomationActions
Set up specific automation actions, such as Teams notifications, ServiceNow tickets, webhooks and archiving teams.
- Guides › AutomationAdd an automation
How to add an automation in Rencore Governance, directly from a policy or from the Automation page.
- Guides › AutomationArchive inactive SharePoint sites
Find SharePoint sites nobody has used for months, ask the owners if they still need them, and set the unused ones to read-only or archive them.
- Guides › Automation › ActionsArchive or unarchive a team with an automation
How to add the Archive or Unarchive a Team action to an automation, and how the Archive Unused Teams template uses it.
- GuidesAutomation
Automations in Rencore Governance run steps such as sending an email or disabling a user account when a trigger fires, for example a policy violation.
- Guides › AutomationChoose a trigger for an automation
The triggers that can start an automation in Rencore Governance, such as manually, on a schedule or on a policy violation, and when to use each one.
- Guides › AutomationClean up after a leaver
Find accounts of people who left, with the licenses, workspaces and OneDrive content they still hold, and remove their access with actions or an automation.
- Guides › AutomationClean up redundant, obsolete and trivial content
Find old, unused and trivial files in SharePoint and OneDrive before a Copilot rollout, then archive the files or the Teams and sites that hold them.
- Guides › AutomationCreate a custom automation
How to build an automation from scratch in Rencore Governance: choose a trigger, then add steps such as an email, a Teams message or a Power Automate flow.
- Guides › AutomationCreate an automation from a template
How to add an automation from the Automations Template Library in Rencore Governance, then adjust its trigger, steps and settings before you save it.
- Guides › AutomationCreate an automation summarized by policy
How to set up an automation that runs once per related object for a policy that is summarized by that object, instead of once per violation.
- Guides › Automation › ActionsCreate ServiceNow tickets with an automation
How to create ServiceNow incidents from a Rencore Governance automation that calls the ServiceNow REST API.
- Guides › Automation › ActionsDelete a Claude project
This automation action permanently deletes a Claude project, including its custom instructions and knowledge documents, through the Anthropic Compliance API.
- Guides › AutomationExport an automation
How to export an automation from Rencore Governance as a file, so you can import it into another Workspace or Environment.
- Guides › AutomationImport an automation
How to import an automation file into Rencore Governance, for example one exported from another Workspace or Environment.
- Guides › Automation › ActionsRemove SharePoint file versions
An automation action that deletes older versions of a SharePoint file, keeping the current version plus the number of major and minor versions you choose.
- Guides › Automation › ActionsSend a Teams notification for policies
How to post a message to a Teams channel from a Rencore Governance automation with an incoming webhook.
- Guides › AutomationTrigger a manual automation
How to run an automation with a manual trigger on an object from the Rencore Governance inventory, for one object or several at once.
- Guides › Automation › ActionsTrigger a webhook for Power Automate
How to trigger a Power Automate flow or another external webhook from a Rencore Governance automation with Send HTTP request or Trigger webhook.
- Guides › AutomationTroubleshoot automation errors
How to find out why an automation failed: open its Automation Batch Page, find the batch in error and read the details of each failed run.
- Guides › AutomationView automation batches
The Automation Batch Page groups all runs of one automation by the time they were triggered, so you can see what each batch did and spot errors.
Concepts 2
- ConceptsBuilt-in actions, automations and automation actions
Built-in actions, automations and automation actions all change objects in Rencore Governance, but each one is started and used differently.
- Concepts › NotificationsEnterprise automation notifications
Changes to automations in Rencore Governance: scheduled automations run on their own schedule and policy violation automations trigger until fixed.
Use cases 2
- Use cases › What do you want to do?Archive or delete inactive workspaces
Find Teams, sites and communities nobody uses anymore, ask the owners whether they are still needed, and archive or delete the rest.
- Use cases › What do you want to do?Connect governance to your ticket system
Open a ticket in ServiceNow or another ticket system, or start a Power Automate flow, when a policy finds a violation or an automation runs.
Reference 45
- ReferenceAutomation actions
Every action a Rencore Governance automation can run, grouped by connector, with the number of actions for each one.
- Reference › Automation actionsAutomation actions for ChatGPT Enterprise
The 9 actions Rencore Governance automations can run on ChatGPT Enterprise, with a description and category for each.
- Reference › Automation actionsAutomation actions for Claude Enterprise
The 1 action Rencore Governance automations can run on Claude Enterprise, with a description and category for each.
- Reference › Automation actionsAutomation actions for Copilot Studio
The 4 actions Rencore Governance automations can run on Copilot Studio, with a description and category for each.
- Reference › Automation actionsAutomation actions for Microsoft 365
The 50 actions Rencore Governance automations can run on Microsoft 365, with a description and category for each.
- Reference › Automation actionsAutomation actions for OneDrive
The 2 actions Rencore Governance automations can run on OneDrive, with a description and category for each.
- Reference › Automation actionsAutomation actions for Planner
The 1 action Rencore Governance automations can run on Planner, with a description and category for each.
- Reference › Automation actionsAutomation actions for Power Apps
The 4 actions Rencore Governance automations can run on Power Apps, with a description and category for each.
- Reference › Automation actionsAutomation actions for Power Automate
The 2 actions Rencore Governance automations can run on Power Automate, with a description and category for each.
- Reference › Automation actionsAutomation actions for Power BI
The 2 actions Rencore Governance automations can run on Power BI, with a description and category for each.
- Reference › Automation actionsAutomation actions for SharePoint
The 41 actions Rencore Governance automations can run on SharePoint, with a description and category for each.
- Reference › Automation actionsAutomation actions for Teams
The 15 actions Rencore Governance automations can run on Teams, with a description and category for each.
- Reference › Automation actionsAutomation actions for Viva Engage
The 4 actions Rencore Governance automations can run on Viva Engage, with a description and category for each.
- ReferenceAutomations
The automation templates Rencore Governance provides, grouped by connector, with the number of templates for each one.
- Reference › AutomationsAutomations for ChatGPT Enterprise
The 18 automation templates Rencore Governance provides for ChatGPT Enterprise, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Claude Enterprise
The 2 automation templates Rencore Governance provides for Claude Enterprise, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Microsoft 365
The 4 automation templates Rencore Governance provides for Microsoft 365, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for OneDrive
The 3 automation templates Rencore Governance provides for OneDrive, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Power Apps
The 4 automation templates Rencore Governance provides for Power Apps, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Power Automate
The 2 automation templates Rencore Governance provides for Power Automate, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for SharePoint
The 9 automation templates Rencore Governance provides for SharePoint, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Teams
The 9 automation templates Rencore Governance provides for Teams, with what each one does and the objects it applies to.
- Reference › AutomationsAutomations for Viva Engage
The 2 automation templates Rencore Governance provides for Viva Engage, with what each one does and the objects it applies to.
- ReferenceBuilt-in actions
The built-in actions you can run on inventory objects in Rencore Governance, grouped by connector.
- Reference › ActionsBuilt-in actions for ChatGPT Enterprise
The 9 built-in actions you can run on ChatGPT Enterprise objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Claude Enterprise
The 1 built-in action you can run on Claude Enterprise objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Microsoft 365
The 24 built-in actions you can run on Microsoft 365 objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for OneDrive
The 3 built-in actions you can run on OneDrive objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Power Apps
The 4 built-in actions you can run on Power Apps objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Power Automate
The 4 built-in actions you can run on Power Automate objects in Rencore Governance, with what each one does and the objects it applies to.
Show all 45 pages
- Reference › ActionsBuilt-in actions for SharePoint
The 19 built-in actions you can run on SharePoint objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Teams
The 11 built-in actions you can run on Teams objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ActionsBuilt-in actions for Viva Engage
The 2 built-in actions you can run on Viva Engage objects in Rencore Governance, with what each one does and the objects it applies to.
- Reference › ConnectorsChatGPT Enterprise
What Rencore Governance covers for ChatGPT Enterprise: 33 object types, 30 policies, 18 automations and 9 built-in actions, grouped by product area.
- Reference › ConnectorsClaude Enterprise
What Rencore Governance covers for Claude Enterprise: 21 object types, 17 policies, 2 automations and 1 built-in action, grouped by product area.
- Reference › ConnectorsCopilot Studio
What Rencore Governance covers for Copilot Studio: 12 object types and 10 policies, grouped by product area.
- Reference › Automation actionsGeneral automation actions
The automation actions that are not tied to one connector, such as sending an email or a webhook, with a description and category for each.
- Reference › ConnectorsMicrosoft 365
What Rencore Governance covers for Microsoft 365: 11 object types, 29 policies, 4 automations and 24 built-in actions, grouped by product area.
- Reference › ConnectorsOneDrive
What Rencore Governance covers for OneDrive: 4 object types, 7 policies, 3 automations and 3 built-in actions, grouped by product area.
- Reference › ConnectorsPower Apps
What Rencore Governance covers for Power Apps: 4 object types, 3 policies, 4 automations and 4 built-in actions, grouped by product area.
- Reference › ConnectorsPower Automate
What Rencore Governance covers for Power Automate: 6 object types, 13 policies, 2 automations and 4 built-in actions, grouped by product area.
- Reference › ConnectorsPower BI
What Rencore Governance covers for Power BI: 12 object types and 10 policies, grouped by product area.
- Reference › ConnectorsSharePoint
What Rencore Governance covers for SharePoint: 14 object types, 32 policies, 9 automations and 19 built-in actions, grouped by product area.
- Reference › ConnectorsTeams
What Rencore Governance covers for Teams: 10 object types, 22 policies, 9 automations and 11 built-in actions, grouped by product area.
- Reference › ConnectorsViva Engage
What Rencore Governance covers for Viva Engage: 1 object type, 1 policy, 2 automations and 2 built-in actions, grouped by product area.
FAQ 2
- FAQDo I need to set up automations?
No, automations are optional. Without them, reviewers can still complete reviews and make changes to workspace access. Automations add post-review actions and…
- FAQWhat are the limitations of automations?
An automation runs at most once a day per object, each run can take up to 4 hours, and a threshold limit or the daily API limit can stop it early.
Glossary 11
- GlossaryAutomation
An automation is a workflow Rencore Governance runs on inventory objects when a trigger fires. It has one trigger and one or more steps, and each step runs an…
- GlossaryAutomation action
An automation action is a single operation an automation step performs, such as sending an email or archiving a Team. The actions available depend on the…
- GlossaryAutomation batch
An automation batch is the group of automation runs that started from the same trigger at the same time. Opening a batch shows each run with its result.
- GlossaryAutomation threshold
An automation threshold, or threshold limit, caps how many objects an automation processes in one day. It is a percentage or a number of objects.
- GlossaryBuilt-in action
A built-in action is a ready-made operation you run directly on inventory objects without building an automation, for example adding a user to a Team.
- GlossaryCategory
A category groups policies, reports and automations by governance goal, such as Security or Costs. The template libraries filter by category.
- GlossaryContext change
A context change is an automation step that switches the objects the next actions run on. For example, it moves from a team to all of its channels or to its…
- GlossaryCriticality level
A criticality level, Low, Medium or High, rates how much impact an automation or built-in action has on your tenant. Roles carry separate permissions to…
- GlossaryData placeholder
A data placeholder is a field in double curly braces, such as {{reviewers.names}}, that Rencore Governance fills with real data when it sends a message.
- GlossaryLeaver
A leaver is someone who has left your organization but whose account may still hold licenses, workspaces, ownership and OneDrive content. Rencore Governance…
- GlossaryWebhook
A webhook is a URL another system listens on, so that a call to it starts something there. In Rencore Governance, the automation actions Trigger webhook and…