Added new Access & Identity use case

[MikeAdamsMews]

Summary

• Added new use case for Access & Identity Management

Follow style guide

Style guide

Check during review

• The changelog and potentially a deprecation entries are in place.
  • The changelog timestamp is date of merge to develop.
• JSON example extended.
  • New properties are added to the correct place in the JSON.
• New properties in the table are added to the correct place.
• Correct formatting:
  • Spacing is consistent between titles, sections, tables, ...
  • Correct JSON format - indentation.
• DateTime properties should always be defined in ISO format.

[jirrick]

This doesn't seem to describe the actual use case, rather just list our operations with very little business usage. There are some properties which seem to use this, maybe ask them about the particular scenarios?
cc @stang704

[stang704]

This doesn't seem to describe the actual use case, rather just list our operations with very little business usage. There are some properties which seem to use this, maybe ask them about the particular scenarios? cc @stang704

it looks like there's 3 partners using it - Akia, Duve, Brivo Access Integration

let's ask TPSM if they know much about these partners' workflows

[MikeAdamsMews]

Will be discussed with @stang704 tomorrow - so may add some content to address the points made.

[stang704]

Discussed on call with Mike.

We'd do something like the Housekeeping use case, and include information around how an integration partner might incorporate this into their workflow. See below

Preamble:
(something about what are resource access tokens), currently supported types are RFID serial numbers or pin codes.

The resource access token endpoints are simply a means to store access information per reservation (and if access is specific to a guest - companionship) --> maybe link to the Mews glossary about companionships on reservations. These endpoints do not trigger any specific action in Mews. Depending on the properties desired guest experience flows, the property can plug in other systems to utilise this information: e.g. a tool to display the access information to verified guests, a POS/middleware system to allow guests to pay with their wristband room key at various F&B outlets and post charges to their billing.

Set up:
If you're an integration partner, you may need to first have the rooms mapped between Mews and your system. Use resources/getAll to get a list of all rooms at the property. Depending on the events that trigger a key delivery to the guest, you may want to subscribe to webhooks/websockets or use reservations/getAll (to be notified of check-ins) to fetch reservations corresponding to a certain arrival time period (e.g. arrivals today).

Storage:
Once a key is created, you can then push that information into Mews using the resource access token add

If a key is no longer valid before the indicated validity interval, for any reason, you can update or delete the access token and issue a new one if needed.

Further applications:
A guest portal/digital concierge app can fetch the access information related to the reservation (and companionship, if applicable), and display the information to the guest in the app.

[MikeAdamsMews]

Just a quick note, I haven't forgotten this PR, I've just not had the time to follow up on it! I will progress it during the first week in November.

[vitezp]

@MikeAdamsMews is this PR ready for review? If you didn't have time to follow-up on the comments that's fair, however either close and reopen the PR once ready, or we should somehow mark i here, Thanks