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 10 Next »

Customer roles can be used to limit products to be visible only to customers in certain roles.  This allows resorts to create products for specific customers for their role assignment. Roles can also be used to manage Administrator access in Aspenware Commerce.

Setup Checklist

This section is a comprehensive and high-level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.

1. POS Tasks

 

RTP|One Only

  • Ensure that RTP|One General Program Profiles are set up. REQUIRED

PREREQUISITE

2. Aspenware Commerce Tasks

 

  • Disable Ignore ACL rules (sitewide). To disable, go to Configuration > Settings> Catalog settings. Within the performance section, uncheck Ignore ACL rules (sitewide). REQUIRED

PREREQUISITE

1. Create Nopcommerce Customer Roles REQUIRED

  • Go to Customers > Customer Roles page in admin, select Add new.

    • Enter a Name and System name for the role.

    • Check Active

    • Click Save.

**If using Siriusware, this step is complete, If using RTP|One, continue to the next step.

  • Go to the Aspenware Commerce > Role Configuration

  • Choose the Customer Role from the Role drop-down.

  • Next, depending on what “roles” are being mapped to this role from external systems, fill in the additional role ids as follows:

    • External Role Id: Enter the General Program Profile ID.

    • Sales Channel ID and Membership Type ID: Leave these blank.

2. Manage Admin Users OPTIONAL

  • Ensure that the user who should be assigned admin access has created an account or has logged into the store site using their POS or authentication profile credentials.

  • Go to Customers > Customers page in Admin.

  • In the Email field, search for the user’s email address. 

  • Click the Edit button beside the appropriate user.

  • Click in the Customer roles field and select ‘Administrators’ from the drop-down list. 

  • Click Save.

  • If two-factor authentication for admin is turned on in live, then send the Admin a Two-Factor Message to set up their Google Authenticator code.  

DETAILED SETUP

Prerequisite Tasks

This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.

1. POS Tasks

RTP|One Only

  • Nopcommerce Customer Roles map to General Program Profiles. General Program Profiles should be set up in RTP|One and assigned to customers ahead of completing the following configuration to map Customer Roles in Nopcommerce to RTP|One General Program Profiles. 

  • To set up General Program Profiles in RTP|One:

    • Go to Admin > Search > Search for general program > you will see the list of previous GPPs set up at the top, to add a new one > Action > Create

    • Enter the Code, Display Order, and Description > Save

    • You can add roles to individuals through Customer Manager > Search for your customer > Special Profiles > General Program Profiles > Add New > select the general program you just created > OK 

2. Aspenware Commerce Tasks

  • In order for customer roles to work, the following setting must be disabled: Ignore ACL rules (sitewide). To disable, go to Configuration > Settings> Catalog settings. Within the performance section, uncheck Ignore ACL rules (sitewide).

Setting

Value

catalogsettings.ignoreacl

False

Detailed Setup Guide

This section describes all required steps to set up the feature after prerequisite tasks have been completed.

1. Create Nopcommerce Customer Roles

  • Go to Customers > Customer Roles page in admin, select Add new to add a new Customer Role in Nopcommerce. (Even if a General Program Profile is already set up in RTP|One, a Nopcommerce Customer Role must also be set up so this role can be mapped to the General Program Profile and/or Membership role.) 

    • Enter a Name and System name for the role. This can be the same entry for both.

    • Check Active

    • Click Save.

**If using Siriusware, this step is complete. If using RTP|One, continue to the next step.

  • Go to the Aspenware Commerce > Role Configuration page to map the newly created Nop Customer Role to an RTP|One General Program Profile. 

  • Choose the Customer Role from the Role drop-down.

  • Next, depending on what “roles” are being mapped to this role from external systems, fill in the additional role ids as follows:

    • External Role Id: Enter the General Program Profile ID from RTP|One if mapping an RTP|One General Program Profile Role.

    • Sales Channel ID and Membership Type ID: Leave these blank, they are only used for EZLinks Golf integrations and are explained in Golf documentation.

2. Manage Admin Users

  • Ensure that the user who should be assigned admin access has created an account (if they do not have an existing account in the POS) or has logged into the store site using their POS or authentication profile credentials.

  • Go to Customers > Customers page in Admin.

  • In the Email field, search for the user’s email address. 

  • Click the Edit button beside the appropriate user.

  • Click in the Customer roles field and select ‘Administrators’ from the drop-down list. 

NOTE: If a phone number is required, you may need to enter a dummy phone number for the admin user to save changes.

  • Click Save. The customer should then have access to the Administration link in the utility bar when they log in to the site. 

  • If two-factor authentication for admin is turned on in live, then send the Admin a Two-Factor Message to set up their Google Authenticator code. 

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