Retention policies

Created by Louise Persson, Modified on Fri, 31 Jan at 3:27 PM by Didde Skov

It is possible to configure "Retention Policies" for integrations in Board.
As a data owner, it is important to ensure that only relevant information is stored and only for an appropriate period. Retention rules help ensure that, among other things, personally identifiable information is deleted after a specified time. 


You must be an administrator to configure retention policies.


You can create as many retention policies as you need.

How to set up "Retention Policies": 

  1. Go to "Settings."
  2. Click on the "Integrations" menu item.
  3. Select the integration for which you want to configure retention policies.
  4. Click on "Retention Policies."
  5. Click the green "+Create Retention Policy" button.
  6. Toggle whether the retention policy should run automatically. This means the policy will be executed nightly.
  7. Select the data set for which the retention policy will apply.
  8. Choose the date field in the dataset.
  9. Specify the number of days after which data should be deleted.
  10. Select the type of retention policy to be applied.
  11. Click "Save."


After creating a retention policy, you can view an overview under "Retention Policies" of what has been set up and executed. Specifically, you will get an overview of the following: 

  • Is it set to run automatically? Yes/No.
  • Which data set is selected.
  • Which field is being deleted.
  • Which type is selected.
  • How many days before data is deleted.
  • When the retention policy last ran.
  • How many items were affected.


Additionally, you have 4 options for managing your retention policies: 

  1. Run the retention policy manually.
  2. View a log of the dates and times when the job was executed. You can also see how many items were affected each time the job ran.
  3. Edit the retention policy.
  4. Delete the retention policy.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article