sQuid - XOD data scopes - Access to staff home addresses

[David44]

Hi,

 

Is anyone else using sQuid for payments? We planned to migrate to them over the summer after Pay360 closed down at the end of July. The first step is to sync data via Groupcall XOD. When we went through this process it turns out they were requesting 'Access to staff home addresses' which they have no need for. We have gone back and forth with them but on the rare occasion they do respond, they give vague answers implying it's Groupcall's issue and they seem unable or unwilling to remove this scope.

 

If you use sQuid, do they have the 'Access to staff home addresses' scope enabled in XOD? How have you justified them having this?

 

Thanks

David.

[CTIDTech]

Can you not filter the fields in Groupcall to ensure you only share the necessary fields for the purpose of the contract. If they cannot restrict this, then I would walk away as potential GDPR breach - What does your GDPR policy state?

[David44]

I don't believe we can filter the data scopes that we allow them access to. My understanding of XOD is that sQuid (or anyone else) requests the data scopes they say they need and we Approve or Deny the request, we can't change the scopes as a school, it's a binary choice. Unless you know otherwise?

 

We approved the request a few weeks ago but restricted it to only sync student and contact data by using the GDPR opt-in settings within XOD, opting in everyone except the staff. As of yesterday we restricted the SIMS user that XOD uses so that it itself doesn't have 'Access to staff home addresses' and then changed the settings in XOD to opt-out instead, so although in XOD it shows that sQuid have 'Access to staff home addresses', in reality they don't because the user that XOD uses to extract data from the MIS doesn't. All very messy and sQuid are very unresponsive when it comes to tickets (this is far from the only issue). They also haven't explained why they would need 'Access to staff home addresses' for a simple school payment system in the first place.

 

sQuid have claimed that they are unable to change what scopes they request, implying this is a limitation of XOD rather than something they have set up incorrectly. Of course, we already use other systems that use XOD that don't have any need for 'Access to staff home addresses' and therefore don't request that scope so it's very possible for companies to not request this data via XOD. They also claim if they change it, they would have to change it for all schools and not just our school, quite possibly true but that can only be due to the inflexible way they have chosen to create their product.

 

That's why I asked if any other schools were using sQuid and how they dealt with this request for 'Access to staff home addresses', assuming sQuid requests the same data from all schools which is what they claim.

 

Not my choice to walk away or not unfortunately, and we need a payment system for September so too late to move to something else now anyway. Hopefully we won't be using them for too long.

[David44]

Sorry to reply to a thread that I am already the last poster in but the last reply was during the Summer Holidays and maybe people missed it. I'm still wondering if any other school uses sQuid and have had as many issues as us.

 

As well as the issue of them requesting staff home addresses which I mentioned above and sQuid still haven't resolved, we are finding that the system just doesn't work properly.

 

If we add a student to an offer, then find that student within sQuid and select 'View Offers', the offer is not shown against that student. Maybe we are doing something wrong, maybe there is something different about the students this happens to or maybe sQuid just doesn't work as it should. I don't know because they have ignored, or worse, closed without comment, most tickets we raise.

 

Even if you use sQuid and you have had no issues, I would also be interested in hearing about your experience.

@fiza Are you still using sQuid?

[pete]

Cant help with the offers, but that Groupcall report definition file has been created (by Groupcall) to sQuid's specifications.

 

My guess is the sQuid are perfectly capable of asking Groupcall to create another report definition file minus staff details but are unwilling to do so.

 

That unwillingness may stem from their platform being unable to handle imports with those missing fields, or not wanting to pay Groupcall to create an alternative report, but this isn't a problem created by Groupcall.

[David44]

Hi Pete, Yes I agree with what you say. sQuid have been trying to blame Groupcall but I am aware they are not the issue here.

 

I forgot to mention, sQuid sent me an email telling me they had raised the Staff Home Addresses issue with GroupCall and asked them to get in contact with me to talk me through the issue as if it were a Groupcall issue or me doing something wrong. I was then CC'ed in to the reply from Groupcall who rightly told sQuid it was their issue and sent them a link to documentation on how to resolve it.

 

I have not heard anything from sQuid directly.