thirtyone:eight roles
- Lead recruiters… can initiate DBS checks, carry out ID checks and will receive all DBS results
- Additional recruiters… can initiate DBS checks and carry out ID checks
As part of our transition to thirtyone:eight, the DBS verifier role will no longer exist. Moving forward, anyone involved in processing DBS checks, including ID checks, will be referred to as a recruiter. All registered recruiters will have access to thirtyone:eight to process DBS checks. There can only be one lead recruiter, who will receive DBS results and all information relevant to safer recruitment decisions.
Safeguarding hub roles
- Hub owners… can view and edit all hub records. Hub owners can also carry out tasks on behalf of their PCC, find out more in Clearly Simpler’s guide
- Hub administrators… can view and edit hub records
- Hub viewers… can view hub records, but they can't edit them
When setting up your safeguarding hub, you’ll need to decide who will take on the roles of hub owner, hub administrator and hub viewer. You could, for example, match your current dashboard owner to the hub owner. Multiple individuals can be assigned to each role based on your parish’s needs.
GDPR definitions
- A data controller… is the person or body that determines both the purpose and means of the processing, i.e. the why and how (for example, I would like a DBS check run for this person under the agreed protocols)
- A data processor… does not determine the purpose and means of the processing, but instead processes personal data on the instruction of the controller (for example, Your DBS check request has been received and we will now run the check as requested)
In our setting, thirtyone:eight and Clearly Simpler are both data processors: they process personal data when instructed by either PCCs or the diocese, who are data controllers.
PCCs who have a thirtyone:eight subunit are the data controllers for all DBS checks processed on behalf of their subunit. Please note that lead recruiters are not data controllers. Any anomalies should be discussed with the DBF safeguarding team and data protection officer.


