Prism Users Guide - Chapter 31. Centrals
31.3 PRISM_CUSTOM User for Centrals Authentication

About the PRISM_CUSTOM User
Prism includes a special internal user (PRISM_CUSTOM) for customizations. You can use the PRISM_CUSTOM user for centrals authentication and that user will not consume a seat when performing centrals functions. This is especially important for stores that are licensed with a single seat. Using the PRISM_CUSTOM user avoids issues with Centrals going offline because no seats are available.

Configuration at POA:
1. Assign the PRISM_CUSTOM user to the Admin Group.
2. Assign all permissions for performing Centrals tasks to the Admin group.
Sample centrals permissions for user group:

3. Assign the "Home Store" to the PRISM_CUSTOM user.
4. In Store Assignments for the PRISM_CUSTOM user, make sure each location using Centrals is selected.
5. Save the changes.

Centrals Authentication setup - Sample PRISM_CUSTOM employee record with Stores tab selected:

 
Configuration at Store:
Confirm the following:
1. The PRISM_CUSTOM user is configured to assign the Admin Group, allowing all permissions.
2. The "Home Store" has been assigned to the PRISM_CUSTOM user.
3. The Admin Group is assigned the necessary centrals permissions.
4. The Store Assignment is in place.
5. Changes have been saved.

PRISM_CUSTOM User Notes:

• Does not consume a seat license when log in is via API.
• Added to Prism as part of the install process if the user doesn't already exist.
• Has default login credentials of prism_custom/cust0m@2024! (default password can be changed.)
• Can only have its password changed and be assigned to a group. Otherwise, is not editable. 
• When logged in (via API) will have whatever access is provided through group permissions.
• Cannot be deleted but can be inactivated.
• Cannot have its information purged with the PII removal tool.
• Cannot login from the Prism web client.
• If you have multiple customizations, you will have to give the internal user ALL the permissions needed by all the customizations. There is not a separate internal user for each customization.
• In Prism, employees are their own type of record but are also a subset of customer records. The CUST_TYPE flag indicates if the customer is also an employee. The PRISM_CUSTOM user has a corresponding PRISM_CUSTOM customer record (with the CUST_TYPE flag selected.