seven1m
commented
5 months ago @jfloPMM can you give us a better idea of the use case here?
I would expect any report URL you guys attach to a BackgroundCheck record to be a URL back to the Protect My Ministry application. And I would expect that any user who clicks that URL would have to be logged into your application to see the report.
Do you restrict access to the report URL based on login? Assuming the answer is yes, then I expect your customer isn't concerned about who can read the report (since reading the report would require them to log in), but that anyone can see the report URL at all... is that a fair summary?
I don't think we have any plans to add extra permissions around who can see a report URL, but it's also very possible I have misunderstood the issue here.
jfloPMM
shanebonham
Hi, I had a customer inquire as to whether we could change what we return to the background check attribute field for the 'ReportURL'. We currently return a link to the background check report but she does not want ALL users who have access to the Security Badge more details to be able to view that link. She does want them to know the date the check was run and when it expires. My question is whether this can be restricted by a user permission in Planning Center vs us having to return different values to that field based on the organization set up on the Protect My Ministry side. Will this work differently with any future APIs to your knowledge?
{ "type": "BackgroundCheck", "id": "1", "attributes": { "current": true, "note": "string", "status_updated_at": "2000-01-01T12:00:00Z", "report_url": "string", "expireson": "2000-01-01", **"result": "string",_** "completed_at": "2000-01-01T12:00:00Z" }, "relationships": { "person": { "data": { "type": "Person", "id": "1" } } } }