[Rt-commit] rt branch, 4.4/add-gdpr-docs, repushed

[Jim Brandt]

The branch 4.4/add-gdpr-docs was deleted and repushed:
       was 80aca50eaa8ff106a6142df4caec4453362e9ee0
       now fccbc1dbb2a89192547c3c09c10888c9d92fe2c6

1: 80aca50eaa ! 1: c312e42cd8 Add GDPR docs
    @@ -20,7 +20,9 @@
     +
     +=head1 Viewing User Data in RT
     +
    -+User data in RT, like name and email address, are typically stored on a user record.
    ++One of the GDPR provisions asserts a "right of access" for users, meaning they can request
    ++to see the personal data an organization has stored for them. Core user data in RT, like
    ++name and email address, are typically stored on a user record.
     +There are different options to manage how different classes of RT users can view
     +and even edit their user information.
     +
    @@ -68,7 +70,8 @@
     +
     +=head1 Downloading User Data
     +
    -+RT provides several different options to download user data to format-neutral
    ++To allow RT administrators a way to give end users a copy of their data on
    ++request, RT provides several different options to download user data to format-neutral
     +tsv files. These options are available to administrators on the user admin
     +page at Admin > Users > Select > [find a user].
     +
    @@ -119,6 +122,11 @@
     +that have the id. The user record is then deleted. This option is likely the
     +easiest since it automatically handles linked objects in one step.
     +
    ++As with the Anonymize User option, this shredder configuration does not find
    ++references to email address or other data in the body of correspondence.
    ++RT provides a script C<rt-munge-attachments> which you should also run to replace
    ++or remove these references.
    ++
     +To replace with a user other than Nobody, update the replace_relations argument
     +on the shredder page before running.
     +
    @@ -137,3 +145,4 @@
     +See L<RT::Shredder> for information on plugins for other objects.
     +
     +=cut
    +
-:  ------- > 2: fccbc1dbb2 Refine rt-munge-attachments docs clarifying GDPR cases