Customer Visibility: Implementation Checklist
The following sections provide details you can use to ensure that the system is configured properly for restricting the visibility of customer records, and to understand (and change, if needed) the settings that affect the processing workflow.
Implementation Checklist
We recommend that before you initially restrict visibility of customer records, you make sure the needed features have been enabled, settings have been specified, and entities have been created, as summarized in the following checklist.
| Form | Criteria to Check |
|---|---|
| Enable/Disable Features (CS100000) | Make sure the minimal features have been enabled, as described in Company Without Branches: General Information, Company with Branches that Do Not Require Balancing: General Information, and Company with Branches that Require Balancing: General Information. |
| Make sure that the Multi[2]insert2021/11/2915:41:55+03:00b-B[3]-B2021/11/2915:41:56+03:00ranch Support feature has been enabled, if you need to restrict the visibility of customer records for particular branches. | |
| Enable the Customer and Vendor Visibility Restriction[4]insert2021/08/1909:51:55+03:00 feature to perform , feature[5], feature2021/08/1909:52:06+03:00[6]insert2021/08/1909:52:08+03:00 Customer Visibility: To Restrict Visibility to a Company. | |
| Enable the Multicurrency Accounting and Multiple Base Currencies features to perform Customer Visibility: To Restrict Visibility to a New Company. | |
| Customer Classes (AR201000) | [8]This was not explained in the chunk, and the interplay of class settings versus customer settings was not explained. Shouldn't we cover this in the chunk (or if it's described in another chunk, shouldn't we refer to it here and in the GI topic)?2020/10/1121:56:06-04:00Be sure that the customer classes whose visibility you want to restrict have been defined. |
| Customers (AR303000) | Be sure that the customer accounts have been defined for the customers whose visibility you want to restrict.[9]Does a row need to be added (after this) for defining in the system each of the access roles corresponding to branches or companies (I'm talking about creating the roles--not specifiying them for the branches and companies, which you do in the next two rows), or are they automatically created each time you create a branch or company?2020/10/1122:03:11-04:00 |
| Branches (CS102000) | Make sure that for each branch to which the visibility of any customers should be limited, the appropriate role associated with the branch is specified in the Access Role box (Configuration Settings section) on the Branch Details tab. |
| Companies (CS101500) | Make sure that for each company to which the visibility of any customers should be limited, the appropriate role associated with the company is specified in the Access Role box (Configuration Settings section) on the Company Details tab. |
| Users (SM201010) or User Roles (SM201005) | Make sure that the needed users have been assigned to the roles specified for branches and companies. For details, see User Roles: General Information. |
Validation of Configuration
To make sure that all configuration has been performed correctly, we recommend that in your system, you perform instructions similar to those described in Customer Visibility: To Restrict Visibility to a Company[10]insert2021/08/1912:00:26+03:00 and Customer Visibility: To Restrict Visibility to a New Company.