Crew Integration Opinion and Discussion

Hi ​@Wabbles! Thanks for reaching out. 

Regarding your specific concerns, here’s what I found out:

• Crew is granted access to the Reservations API to determine reservation statuses, check-in/check-out times and other information  that may be relevant to their features.
• Our technical documentation outlines the reservation data accessible by Crew. With their current scopes (screenshot), they do not have access to the financials, review and smartlock_code fields and respective sub-fields. All other fields are part of the default reservation scope and cannot be narrowed further. However, having access to a field does not necessarily mean it is used by Crew’s features.
• Crew's access is governed by their privacy policy and our partnership agreement

I hope this helps. 💜

Hey Petra, 

but that’s kind of my point, it does not support any features they offer, even in the scope of what you describe. Crew’s privacy policy only protects my personal data and in no way, shape or form prohibits them from selling any data they collect through an integration to third parties. I don’t know what your partnership agreement covers.

And then at the end of this I still wonder what I get out of this. If there was like an update such as “Bin return successful” or something this would make sense, but as it stands all the user gets is that Crew gets a lot of data they do not need for the provided service.

Cheers,

Thomas

Hi ​@Wabbles   Frances here from the Platform team. 

Thanks for sharing your concern. In our system, guest details are attributes of the reservation resource, so when an integration requests access to our reservation endpoint, it also receives those fields. At the moment we don’t provide a separate permission scope that splits guest details away from reservation data.

To clarify, this isn’t something Crew specifically requested in order to provide their service. It’s simply how the reservation scope currently works within our API.

But I have taken note of your feedback and will discuss with the team regarding separating the guest scope from the reservation scope so that it can be added only when a feature has a use for it.