Establishing GDPR consent when the person doesn&#39;t access a system themself
<p>My company hosts an online database for organisations to manage training data for their people.  </p>

<p>In most cases, administrator users (team leaders/line managers) manage data for their staff/teams.  From an organisation of say, 500 people, usually only around 30 people might ever log in and view data for their teams.</p>

<p>I'm currently trying to understand how the new GDPR regulation regarding consent will be relevant/applied:</p>

<blockquote>
  <p>(32) Consent should be given by a clear affirmative act
  establishing a freely given, specific, informed and unambiguous
  indication of the data subject's agreement to the processing of
  personal data relating to him or her, such as by a written statement,
  including by electronic means, or an oral statement. This could
  include ticking a box when visiting an internet website, choosing
  technical settings for information society services or another
  statement or conduct which clearly indicates in this context the data
  subject's acceptance of the proposed processing of his or her personal
  data. Silence, pre-ticked boxes or inactivity should not therefore
  constitute consent. Consent should cover all processing activities
  carried out for the same purpose or purposes. When the processing has
  multiple purposes, consent should be given for all of them. If the
  data subject's consent is to be given following a request by
  electronic means, the request must be clear, concise and not
  unnecessarily disruptive to the use of the service for which it is
  provided.</p>
</blockquote>

<p>How therefore can organisations like ours realistically provide this, when many people won't actually see/access their own data?  Is consent still required here?  Can that consent be managed by the central point of contact at the client (outside our software)?</p>

<p>I've looked at over a dozen sites providing "advice", but each re-hash the same generic information that doesn't provide enough clarity.</p>

<p>I believe in this case, your company (OrgX) is a data processor and your customer's organization (OrgY) is the data controller.</p>

<p>OrgY is responsible for establishing a lawful basis for sending you (OrgX) the personal data for their employees. Note that <em>consent</em> is just one of six lawful bases outlined in article 6(1). I'm no expert, but I believe OrgY's admin can claim they have a <em>legitimate interest</em> in sending their employee's personal data for training sake. In either case, the data processor is not responsible for establishing the lawful basis for processing.</p>

<p>Of course, data processors aren't completely off the hook. GDPR outlines specific requirements for data processors (see chapter 4, particularly article 28).</p>

consent gdpr