Identity Implementation Worksheet

Owned by Jenni Buonanni
Last updated: Apr 15, 2024 by Becky Haire
4 min read
  1. Identify which applications (clients) you will be integrating with Aspenware Identity. For each application (client), call out if any of the decisions below differ for any one of these applications. NOTE that whenever a new application (client) is onboarded with Identity, some implementation is required.
Aspenware Commerce
Aspenware Arrival
Mobile Application
Other
  1. Are you integrating 3rd party applications with Aspenware Identity? This refers to anything other than Aspenware Commerce and Aspenware Arrival.
Schedule a developer integration call with Aspenware representative and developers.
Share both Identity Hub documentation and Identity Technical Integration guide with 3rd party developers.
Schedule recurring check-in calls with your Aspenware representative and 3rd party developers to get questions answered as they work through the integration.
If desired, ensure that Identity settings are configured in a way that when a guest logs out of Identity in Commerce, for example, they are also logged out of the 3rd Party app.
Ensure the GTM ID for each application, client, is shared with your Aspenware representative if unique per app.
  1. Are you in a multi-resort environment?
No
Yes
  1. Which of the following best explains your multi-resort Commerce configuration.
Separate Aspenware Commerce Instance (multiple admins) for multiple stores, and pointed to single RTP|One instance.
Single Aspenware Commerce Instance (single admin) that multiple stores share but each store has a unique store-front, pointed to single RTP|One instance.
Separate Aspenware Commerce Instance (multiple admins) for multiple stores, and pointed to separate RTP|One instances for each store.
Some combination of the above (please explain details)
  1. If resorts share an RTP|One instance, we recommend a single identity server, which requires a single Identity URL to be used, i.e. login.yourparentcompany.com. Each unique resort can have custom branding, messaging and settings applied to identity, but the URL is shared. What URL do you plan to use for identity?
  2. Complete language strings and theming steps for each resort. Settings can differ from resort to resort as well. If you desire differences between resorts, make your Aspenware representative aware of differences in your implementation.
  3. Ensure the GTM ID for each resort is shared with your Aspenware representative if unique per resort and that your GTM setup is configured to support cross-domain tracking.

 

  1. Decide on a URL you plan to use for identity, such as http://login.resortname.com . Once you’ve decided on a URL, you’ll work with Aspenware to set up SSL and DNS for this Identity URL.
  2. Do you want to allow customers to log in or claim an account using their pass media/RFID number?
  3. Do you plan to use Sendgrid or Inntopia Marketing Cloud as the email sending platform that is integrated into Identity? Once you’ve decided on an email provider, you’ll work with Aspenware to set up the email integration for Identity.
  1. Aspenware offers the ability to text a code to a guest that has an account to verify that they are the owner, would you like to use Aspenware’s Twilio account and number or configure your own Twilio account? Once you’ve decided on a Twilio configuration, you’ll work with Aspenware to set up the email integration for Identity.
  1. Do you want to require that customers reset their passwords after a configurable period of time? If so, consult the configuration guide for reset password setting options and discuss with your Aspenware representative.
  2. Do you have guest checkout (including selective guest checkout) configured in any capacity for your store? If so, make your Aspenware representative aware so that the required settings can be adjusted.
  1. Do you want to enforce lockouts for customers with a configurable number of failed login attempts, if so how long do you want to enforce the lockout for? Consult the configuration guide for lockout setting options and discuss with your Aspenware representative.
  1. What age restrictions do you have in place for allowing customers to create accounts? 13 years old is the default cutoff age. Notify your Aspenware representative if you desire a different setting.
  2. Do you want to enable customers to opt into or out of marketing communications (setting their RTP|One Communications Profile) when creating an account in Identity? If so, discuss with your Aspenware representative.
  1. Do you want to default everyone creating an account to be opted-in to marketing, forcing them to deselect the checkbox to opt-out, or to be opted-out by default, offering the option the check the box and opt-in?
  1. Do you want to enable reCAPTCHA on Identity? If so, discuss with your Aspenware representative after creating your account with Google reCAPTCHA.

For each unique resort theme, provide Aspenware with the following…

Analytics

GTM ID(s)
Ensure you’ve completed the GTM setup for Identity.

Email

Logo file to be used in all emails sent from Identity
Link to the resort’s website (logo image in emails will link here)
Resort Name as you’d like it displayed
Resort Address (to be used in the email footer)

Content

Theme

NOTE: A single custom font can be supported for those who use CSS to import their custom fonts. Font customizations will apply to the Identity application, but the email font will be standardized as Helvetica for all customers. Supply the font URL to your Aspenware Representative, similar to the example below: