Versions Compared

Version Old Version 5 New Version 6
Changes made by

Ilias Sersar

Madrigal Totayo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this section you can choose what to do with certain fields of the persons data when the expiration period has been met.

Image Removed

The fields you need to fill out are as follows:

  • Default expiration period: Here, the choice can be anywhere between 1 month to several years.

    • When expiring: Here the choice can be

    Microbizz's GDPR handling can be set up in the User module, the CRM module, Task module, Project module and the Person module.

    The GDPR handling allows to specify what should happen when a person expires. This is to prevent that you retain old data for employees that have left your company long ago.

    Each person has an expiration date; when the date is reached the person is deleted or some of the person's data is cleared.

    The person gives consent by accepting the GDPR consent agreement which you have created; they receive a mail or similar containing a link to the GDPR consent agreement. The agreement cannot be edited once it has been published. 

    Image Added

    Here you'll find the following settings:

    • Default expiration period: When the user is edited the Microbizz will suggest an expiration this far into the future 
    • When expiring: What should happen when the expiration date is reached. Choose between one of the following:
      • Do nothing
      • Anonymize the selected data fields:
        • When
    expiration date has been met, don't do anything
  • Anonymize the person data fields: The fields ticked off to the right are anonymized
  • Delete the person: Delete the entire person
    • Person data fields: Choose any of the fields in a person's data that needs to be amended
        • anonymizing data, also delete...: Specify which additional data that should also be deleted when the expiration date is reached
      • Delete the task
    • Users should give consent in regards to GDPR by default: If this is set then a GDPR content mail is sent automatically to the users, otherwise the mail is only sent when you request it
    • Mail text for requesting consent: This is the mail text that is included when a mail is sent to the users to request GDPR content
    • Person data fields: These fields should be cleared when the expiration date is reached, this should be the fields containing sensitive personal data

    The "Request consent from all" button this will request consent from all users.

    Requesting consent

    When consent is requested for a user, a mail is sent to all the user who do not have web access to Microbizz. The mail contains the mail text from above, and a link to the a web page where they can see the agreement and accept it.

    For users with web access to Microbizz a GDPR accept page will appear the next time they log in.

    On the user search page you may select one or more users and then select "Request GDPR consent again". On the same search page you can enable the columns "Version accepted" and "Version requested" to see which agreement version have been accepted/requested for the users.

    For persons the mail is sent to the persons email address. For companies the mail is sent to the company email adress.

    Edit consent agreements

    You can have multiple consent agreements, but you can only edit the unpublished ones. When an agreement is published it may possibly be sent automatically to all relevant users. When the users goes to see/accept the agreement, they will always see the latest published agreement.

    When you publish an agreement it is given a version number. When the user accepts the agreement the version number is stored with the user.

    Send test to me

    The "Send test to me" button sends a test mail to you, so that you can see how the GDPR consent agreement looks.

    Image Added

    Table of Contents