Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Error rendering macro 'excerpt-include' : No link could be created for '[TEMPLATE]Feature Landing Page'.

This feature is supported for: {example 1}, {example 2}, and {example 3}

This feature is NOT supported for: {example 1} and {example 2}

Key Terms

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}

Feature Description

Aspenware Commerce and resort mobile apps can optionally use Identity for authentication. Once 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 Aspenware Commerce and the mobile app, so they can seamlessly navigate between applications.

  • More secure than standard login as Identity can require guests to reset their password if the password change date in RTP is past today’s date.

Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.

  • No labels