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
  • Introduction
  • Setting up a collection email
  • Key Features
  • Attachment Management
  • Finding Objects Generated from a Collection Box
  • Success Notification

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

  1. Features
  2. Advanced configuration

Incoming mail data collection

Learn how to set up a data collection email box

Dernière mise à jour il y a 8 mois

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

Introduction

This integration allows you to automatically create objects in Dastra from emails received at dedicated email boxes. Dastra provides these boxes and automates the conversion of incoming emails into objects within the Dastra application.

Five types of objects can be associated with these collection email boxes:

  • Tasks

  • Data Processing

  • Data Subject Requests

  • Contracts

  • Data Breaches

Setting up a collection email

To set up a collection email for any of the objects listed above, go to your workspace settings, under the Integrations tab, and select the "Incomin mail data collection" card.

Then, choose the type of object for which you want to set up the integration by clicking on "Add Integration." Note that you can only have one collection email per object type and per workspace.

You have the option to specify the destination organizational unit for the objects created through this collection box during the integration setup. If this field is left empty, objects will be created in the default organizational unit.

By clicking "Create," Dastra finalizes the integration setup and provides you with the email address to use.

Key Features

  • Automatic object creation: Each email received at an associated email box creates a corresponding object in Dastra.

  • Organizational unit configuration: You can set a destination organizational unit during setup. If specified, the object will be created in that unit.

  • Object fields management:

    • Label: The email subject is used as the name of the created object.

    • Description: The email body is used for the description of the created object.

    • Attachments: Email attachments are added to the object, subject to validation conditions.

Attachment Management

Email attachments are added to the object, provided that:

  • File extensions are valid: Only attachments with valid file extensions are retained.

Here are the autorized extensions : 7z, csv, doc, docx, eml, epub, gif, htm, html, jpeg, jpg, json, md, msg, ods, odg, odp, odt, pdf, png, ppt, pptx, rar, rtf, svg, txt, xls, xlsm, xlsx, zip.

  • Images meet minimum size: For image files (jpg, png, gif, etc.), a minimum size of 5 KB is required. This constraint helps avoid including irrelevant images such as email signatures.

Finding Objects Generated from a Collection Box

Objects associated with collection boxes have a 'source' or 'collection origin' field that you can display in table views by showing the source/collection origin column.

All objects generated from a collection box are tagged with "inbound email," making it easy to identify them if needed.

Success Notification

Upon successful creation of an object from an email received at the collection box, an email notification is automatically sent to the address that triggered the integration. This notification confirms that the object has been successfully created in Dastra, providing immediate assurance that the request or action has been processed.

The language of the confirmation email corresponds to the default language of the workspace where the integration is installed (Workspace settings > Default language).

⚙️