To view or create new roles go to the back office > Admin > Manage Employee Roles. You can create as many roles as you'd like and once created these roles must be attached to users. We strongly recommend that you create a test user and assign the new role or permissions to that user before attaching to a real employee and test it to ensure it has the desired outcome.
Customers Management: This determines if the user is able to create or update customer records from the back office and POS.
Doc Rendering Management: This determines if the user can modify document templates which are typically used for receipt printing.
Employees Management: Determines if the user can create or update employee records.
Gift Card Batches Management: Determines if the user can generate new batches of gift card numbers which are typically sent to a printer to be embedded in physical cards.
Gift Card Settlements Management: Determines if the user can generate specialized reporting that helps settle gift card balances across multiple stores. This is typically used in franchise situations where a card is bought at one location and used at another which creates a situation where one store owes another store money.
Gift Cards Management: The ability to manage singular gift cards in the back office (deactivate, etc).
Global Entity Settings Management: Determines if you are able to modify the configuration settings (entity settings) in the back office. These control some of the fundamental settings of the system.
Import Tools: Enable or disable each of the import tools.
Integration Process Management: Integration processes are synchronization processes that blend the Cloud Retailer system to 3rd party software systems like accounting, e-commerce, etc.
Integration Schedule Management: Allows for schedules to be created to determine when data will be synchronized between systems.
Inventory And Sales: The ability to ring up sales at the POS
Inventory Count Management: Inventory counts are where staff go around and count inventory. The users counting inventory only need the ability to "JOIN" an existing count. Usually, a manager is the one responsible for creating the inventory count to prevent people from including/excluding the right/wrong products from the inventory count.
Inventory Purchase Documents Management: Inventory purchase documents are the templates used to print from when creating purchase orders. These can be customized.
Inventory Purchase Order Management: Controls the ability to create and modify purchase orders. The "StatusMgmt" permission controls if a user is allowed to modify if a purchase order is marked as received or not.
Inventory Settings Management: Inventory settings can be found inside each locations settings and determine the max number of products or costs allowed on a PO. These are settings to reduce the likelihood of an error.
Inventory Store Transfer Management: The ability to create inner store inventory transfers.
Label Templates Management: This permission determines if the user can modify the templates for label printing. _The "Print" option determines if the user can print labels from the back office or POS.
List Management: Lists can be used to control certain aspects of the system, for example, which fields may be required on a customer's record (first name / last name, etc).
Locations Management: This determines if a user can create or modify store locations (physical, virtual, or warehouse).
Option Sets Management: Options are used with our "activities park/online ticketing" application as it relates to ticket options.
Order Type Management: Orders are holding pens for transactions. Hold, work order, layaway, special orders are common names our customers give to orders. This determines if a user can create and configure new order types in the system.
Payment Methods Management: Payments are how your customers pay you at the POS.
Place Holder Text Management: Placeholder text is a generic location for string data used for a variety of things that are system operation related. An example is that parts of the POS display are configurable through the placeholder text.
Point Of Sale - this is a group of base settings at the POS. CanAccessPos CanCancelTransaction CanExitPos CanPerformClosingFunctions CanPerformDiscounts CanPerformReturns - this means, to use "return mode" where everything you scan / add to the POS comes up with a negative quantity. CanPerformVoids - void is different than return, it removes a transaction from the system (but a paper trail remains). CanRemoveLineItems - most users do NOT allow users to completely remove line items (no paper trail) and instead have the void line function reduce the quantity at the POS to 0 so that a proper paper trail remains. IsPosSuperUser - This means they can do anything at the POS.
Pos Client Management: This gives the user access to download the latest version of the POS software from the "Admin" menu in the back office.
Pos Commands Usage: This is a grouping off all the POS commands as referenced at the beginning of this article.
Product Categories Management: Product categories are the department, category, subcategory groups associated with products. This setting does NOT have any bearing on a user's ability to set these values on a products record.
Product Change Worksheets Management: Worksheets allow you to schedule price changes for stores or groups of stores in the future. _The "Print" option determines if you can print labels for these changes in advance of the changes taking effect.
Product Sizes Management: Allows for creation of new sizes. Does NOT determine if a user will have the ability to define the size associated with a specific product.
Products Discounts Management: Product discounts are the same as coupons or custom discounts but they are automatically applied at the POS assuming the correct qualifications are met. This determines if the user can create or edit them.
Products Management: This is the ability for a user to modify a product's data elements (price, description, etc).
Query Management: Queries are used by the system to create groups of things (typically products) so that they can be used to filter inside other elements of the system. A discount may use a query to determine which products the discount should apply to for example.
Registers Management: This is where you can manage the POS stations and configure their individual behavior.
Rent Registration Management: This is the configuration for the product group that requires rental registration.
Report Configurations Management: This determines if you can enter the configuration function of the reports and modify the way a report acts. IF the option "Lock From System Setup Changes" is not enabled then as Cloud Retailer updates to a report will be overwritten, regardless of changes a user may have made.
Report Management: The ability to view and memorize reports.
Report Summary Data Management: You can manually create a report summary or create one from a report you're viewing. A report summary is a summarized version of the report that can be used to generate automated email reports or API data end points.
Sales Tax Jurisdictions Management: A tax jurisdiction is a singular specific tax.
Sales Taxes Management: A sales tax is one or more tax jurisdictions combined together to create a tax that is then applied to a product.
Sales Transaction Receipts: This is the ability to view past sales transactions FROM the back office. The ability to view receipts at the POS is managed independently.
Supplier Documents Management: Supplier documents are typically electric invoices that can be imported into Cloud Retailer from a suppliers computer system.
Supplier Management: Suppliers are people you buy product from and are then attached to products and purchase orders.
Supplier Product Management: Supplier product is the ability to assign a product to a supplier as well as the information associated with this like reorder number, lead time, etc.
CloudRetailer.Plugins.LoyaltyIntegration.Pos.AdjustLoyaltyMembership - It allows users to adjust Loyalty points on adjust memberships form on POS system. This can only be disabled if the user role Point Of Sale => IsPosSuperUser = false