| Insert excerpt | |||||||
|---|---|---|---|---|---|---|---|
|
| Tip |
|---|
This feature is supported for: {example 1}, {example 2}, and {example 3} Resorts using RTP|One as a POS. Separate Identity license required. |
| Warning |
|---|
This feature is NOT supported for: {example 1} and {example 2} |
Key Terms
| Excerpt |
|---|
Key Term 1{1-2 sentence definition. Confirm that key term is not defined in another section first. } Key Term 2{1-2 sentence definition. Confirm that key term is not defined in another section first. } |
{Paragraphs, pictures, attachments, etc go here}
not supported for: Resorts using Siiriusware as a POS. |
Feature Description
Aspenware Commerce, Aspenware Arrival, and resort mobile apps can optionally use Identity for authentication. Once - enabling a customer to be signed in across all platforms that use Identity. When Identity is setup and configured, turning on Identity for Aspenware Commerce is enabled through installing a plugin and several settings within the Commerce platform. Benefits to using Identity for Commerce Authentication rather than native Commerce authentication include:
Implicit find-me flows are more likely to catch guests who already have accounts, routing them to find their accounts and decreasing duplicate customers in your POS.
If multiple applications use Identity as an authentication platform, a guest who is logged in to Aspenware Arrival will also be logged into in to Aspenware Commerce and the mobile app, so they can seamlessly navigate between applications.
More secure security than standard login as Identity can require guests to reset their password if the password change date in RTP|One is past today’s date.
Section Links
Insert excerpt
...