rencore.com (opens in a new tab) Start a trial (opens in a new tab)

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

Guides 21

  • Guides › Automation
    Actions

    Set up specific automation actions, such as Teams notifications, ServiceNow tickets, webhooks and archiving teams.

  • Guides › Automation
    Add an automation

    How to add an automation in Rencore Governance, directly from a policy or from the Automation page.

  • Guides › Automation
    Archive 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 › Actions
    Archive 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.

  • Guides
    Automation

    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 › Automation
    Choose 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 › Automation
    Clean 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 › Automation
    Clean 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 › Automation
    Create 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 › Automation
    Create 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 › Automation
    Create 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 › Actions
    Create ServiceNow tickets with an automation

    How to create ServiceNow incidents from a Rencore Governance automation that calls the ServiceNow REST API.

  • Guides › Automation › Actions
    Delete a Claude project

    This automation action permanently deletes a Claude project, including its custom instructions and knowledge documents, through the Anthropic Compliance API.

  • Guides › Automation
    Export an automation

    How to export an automation from Rencore Governance as a file, so you can import it into another Workspace or Environment.

  • Guides › Automation
    Import an automation

    How to import an automation file into Rencore Governance, for example one exported from another Workspace or Environment.

  • Guides › Automation › Actions
    Remove 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 › Actions
    Send a Teams notification for policies

    How to post a message to a Teams channel from a Rencore Governance automation with an incoming webhook.

  • Guides › Automation
    Trigger 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 › Actions
    Trigger 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 › Automation
    Troubleshoot 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 › Automation
    View 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

Use cases 2

Reference 45

Show all 45 pages

FAQ 2

  • FAQ
    Do 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…

  • FAQ
    What 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

  • Glossary
    Automation

    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…

  • Glossary
    Automation 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…

  • Glossary
    Automation 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.

  • Glossary
    Automation 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.

  • Glossary
    Built-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.

  • Glossary
    Category

    A category groups policies, reports and automations by governance goal, such as Security or Costs. The template libraries filter by category.

  • Glossary
    Context 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…

  • Glossary
    Criticality 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…

  • Glossary
    Data 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.

  • Glossary
    Leaver

    A leaver is someone who has left your organization but whose account may still hold licenses, workspaces, ownership and OneDrive content. Rencore Governance…

  • Glossary
    Webhook

    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…