DASTRA
English
English
  • What is Dastra
  • 🇪🇺USEFUL REMINDERS
    • What is GDPR ?
    • GDPR key concepts
      • Personal data
      • Record of processing activities (ROPA)
      • Privacy impact assessment
      • Data retention period
      • Data Subject Rights (DSR)
      • Privacy by design and by default
      • Security measures
      • Data breach notifications
    • Risk management
      • Definition of risks
      • Risk assessment
      • Vendor risk management
  • 🧑‍🎓GETTING STARTED
    • Setting up
      • Create and set up a workspace
      • Create and set up organizational units
      • Appointing a DPO
      • Add a lead authority
      • Invite users
      • Managing roles and permissions
      • Create and assign teams
      • Frequently asked questions
    • Tutorial
      • Step 1: Setting up
      • Step 2: Map your personal data processing and draw up a register
      • Step 3: Managing risks
      • Step 4: Prioritize actions
      • Step 5: Implement internal processes
      • Step 6: Document compliance
    • Support
      • The dastronaut's assistant
      • Online help
      • Request support
      • The customer support process
  • ⚙️Features
    • Dashboard
    • General
      • Advanced Filters
      • Import your data (Excel, Csv)
      • Tag management
      • Custom fields
      • AI Assistant
      • Email templates
    • Data Mapping
    • Record of processing activities
      • "Data controller" record
      • "Data processor" record
      • Establish your record
      • Export / import the record
      • Use a processing activity template
      • Declare a processing activity
      • Complete a data processing activity
        • General information
        • Stakeholders
        • Purposes
        • Dataset
        • Assets
        • Data subjects
        • Data subjects rights (DSR)
        • Recipients
          • Data transfers outside the EU
        • Security measures
        • Impact analysis
        • Documentation
      • Create relationships between processing activities
      • Processing freshness
      • Share the record of processing
      • Data visualization
        • View the treatment tree
        • View the record data map
        • View the transfers map
      • Frequently asked questions
    • Audits and DPIA
      • Create or modify an audit template or DPIA
      • Scheduling an audit or a PIA
      • Share an audit report or PIA
      • FAQ
    • Privacy hubs
      • Create a Privacy hub
      • Configure your Privacy hub
        • Homepage and general configuration
        • Questionnaires
        • Data subject requests
        • Record of processing activities
        • Attachments
        • Organizational chart
        • Contacts
        • Security
        • Appearance and design
      • Preview and share your privacy hub
      • Collecting data processing projects from a Privacy hub.
    • Contracts
      • Declare a Contract
      • Structure of a contract
      • Documents
      • Assets
      • Signers
      • Linked users
      • Sign the contract
      • Docusign integration
      • Contract versions
      • Contract templates
    • Risk management
      • Glossary of terms
      • Risk management process
        • 1. Identification
        • 2. Assess
        • 3. Monitor
        • 4. Control
        • Let's recap
      • Dastra / eBios RM comparison
      • Attach a risk to a processing activity
      • FAQ
    • Planning
      • Create your action plan
      • Create or modify a project or an iteration
      • Monitor, screen or export your tasks
      • Customise the task workflow
      • Share as calendar
      • Customise the task workflow
      • Go further with planning
      • FAQ
    • Data subject right request
      • Manage data subject right requests
      • Set up a data subject right request widget
      • Technical integration
      • API integration
    • Manage data breach notifications
      • Report a data breach
      • Export your data breach notifications
    • Manage cookies consent
      • Widget configuration
        • Preliminary study
        • Cookies scanning
        • Classify cookies by consent categories
        • The purposes of cookies
        • Implement a cookie consent widget
        • Collect proof of cookie consent
        • Go further on cookie consent
        • In case of unavailability
      • Technical integration
        • Functioning of the widget
        • Quick start
          • Wordpress
        • Language management
        • Test the integration of a widget
        • Blocking cookies
          • Blocking iframes (twitter/youtube...)
          • Google Tag Manager
        • Advanced Design
        • Manage consent programmatically
        • User identification
        • Mobile applications
          • Hybrid applications
          • Native applications
        • TCF 1.1/2.0
      • RGAA compliance
      • Breakdown service
    • Regular review (freshness)
    • Custom Reporting
      • Integration with data analysis tools (BI)
    • AI Systems
      • Establishing a record of AI systems
      • Risk analysis and business value
      • Transparency notice
      • AI Models repository
    • Advanced configuration
      • SCIM
      • Roles and permissions
      • Single Sign On (SSO)
        • SAML 2
        • OpenId
        • ADFS
        • Active Directory
        • Okta
        • Known problems
      • References
      • API key management
      • Notifications
      • Workflow steps / process flow
      • Incoming mail data collection
      • OneDrive/Google Drive integrations
      • Webhooks
      • SMTP configuration
      • Workflow rules
      • Message templates
      • Email domains
  • PARTNERS
    • Portal
  • 📄API documentation
    • Configuration
    • Authentication
    • API References
    • Integrations
      • Frequently asked questions
  • 🛡️Security
    • Security at Dastra
    • Security roadmap
    • Quality of Service
  • Certifications
  • 🤖Other
    • FAQ
    • Known problems
    • Changelog
  • Referentials
    • CNIL referentials
      • HR referential from CNIL
Propulsé par GitBook
Sur cette page
  • What is the freshness indicator?
  • How do I activate the freshness indicator?
  • Deactive the freshness option
  • Displaying the freshness indicator
  • Rules for displaying review statuses
  • Review an item
  • Notifications

Cet article vous a-t-il été utile ?

  1. Features

Regular review (freshness)

Dernière mise à jour il y a 10 mois

Cet article vous a-t-il été utile ?

What is the freshness indicator?

Freshness is an indicator of when an item was last reviewed in Dastra. It can be a treatment, an object in your repository or even a contract. By activating this feature you'll define a future review date for the item, and the freshness will degrade as this date approaches. This feature is a simple and fun way of ensuring that you regularly review the information entered in the application.

How do I activate the freshness indicator?

To activate the freshness of an object type, go to your workspace settings and select the Regular reviews tab.

From this menu, you can activate freshness for the various objects that have this feature by clicking on the object selection drop-down menu.

Tick the option to activate regular review of the item and set the desired time interval between each review.

The freshness of an item corresponds to the number of days between the last date on which the item was marked as fresh and its future review date.

The review date is a date in the future calculated from the last date on which the item was marked as fresh, to which we add the desired time interval between each review.

Please note that this expiry interval will be the same for all items of the same type for which the review is active.

Deactive the freshness option

To deactivate the option, simply uncheck the Enable regular item review box in the Regular reviews section of your workspace settings.

Displaying the freshness indicator

All objects with this functionality have a freshness column that you can add to the summary tables. This column is called "Last review date", and allows you to monitor the freshness status of each item.

Please note that freshness is only displayed for published items.

You will also find this indicator in the item shortcut menu.

Rules for displaying review statuses

There are 3 possible freshness statuses: fresh, pending or out of date. By default, the following display rules apply:

Review status
Display rule

Fresh (green colour)

The item has been reviewed recently and does not require immediate attention.

This status is displayed until the current date is within the last 10 percent of the expected interval since the last review.

Pending (orange)

The item needs to be checked.

This status is displayed for the last ten percent of the planned interval since the last review.

Out of date (red)

The item no longer complies with the review policy.

This status is displayed when the current date is greater than the last review date + the defined interval.

Example: I have defined 1 year interval for reviewing data processing activities. For a processing reviewed on 1 January:

  • it will be displayed fresh until 25 November

  • it will be displayed pending 25 November

  • On 31 December, it will then be displayed as out of date until it is reviewed.

Review an item

You can decide to review an item at any time, without necessarily waiting for the next review date. To do this, click on the cell in the fresh column of an item when you are in a table view. Of course, the functionality must be active for this element and you must be displaying the column in question.

This takes you to the item review window. Note that it is possible to consult old reviews from this window.

By reviewing an item, you restart a freshness cycle from the current date until the next review date. The review date is calculated by default according to the item's review interval setting (see above). You can decide to ignore this default date and apply a specific expiry date to this item by ticking the "Change next review date" option and selecting a new date (the next review date must be at least D+1).

Notifications

The creator of the element, as well as the users associated with the element (owners in the case of treatments, for example), will be notified by email when an element reaches the out-of-date state, to remind them that the element has not been revised for a long time and that it is time to refresh it.

⚙️
Freshness indicator operating diagram
The configuration menu for the reg
The list of objects for which you can activate freshness
The freshness column
the freshness indicator in an item's shortcut menu
The item review window