TABLE OF CONTENTS
Navigate to: Customers > Accounts > Users
In this tab, Administrators can add and manage the users associated with a B2B Account. Znode supports B2B Accounts with three role levels; Administrator, Manager, and User.
The roles "Administrator" and "Manager" have Administrator-level roles and do not have restrictions. Administrators of an account can view all orders placed by associated users. Administrators of a parent account can also view the orders placed by the users of an associated child account. The roles "User" can be configured with purchasing settings: "Does not Require Approval", and "sometimes Requires Approval".
Users Details
Detail | Description |
Full Name | The roles "Administrator" Full Name details |
Username | Customer's UserName. |
Email ID | The customer’s email address will be the default. The email address can be edited after it is saved. |
Role Name | Role of the user. |
Department | Department to which the user belongs. |
Pending order History/Order History | Pending Order details can be seen here. |
Order History | Order History can be seen here. |
In the case of Role Name: User
Permission Name | Sometimes Requires Approval : Znode restricts orders based on specified amount limits. Orders exceeding the defined threshold are sent for approval. For example, if an amount range of $100 to $1000 is set at the user level, and the store-level amount is $0, then all orders will require approval. However, if the user-level range is set to $100 to $1000 and the store-level amount is also set to $100, the system works in conjunction with the “Sometimes Requires Approval” setting. In this case, orders below $100 will not require approval, while orders between $100 and $1000 will always require approval. |
Always Requires Approval : Znode supports an “Always Requires Approval” permission, which enforces approver permission for every purchase made by the user. When this setting is enabled, the "Checkout" button is replaced with a "Submit for Approval" option, turning the cart into a Pending Order. The Pending Order is then sent to the designated Approver, as specified in the Approval Name configuration. Once the Approver approves the Pending Order, the user can proceed to create an Order from the approved request. | |
Never Requires Approval: User does not require approval from the Administrator/Manager to purchase Products. | |
Approval Name | Drop-down with Admin and Manager of the respective Department detail |
Budget Amount | This is the Users per transaction purchasing allowance. If Order Total exceeds the Budget amount, the cart will be submitted as a Pending Order. Pending Orders are sent to the Approver after the cart is submitted. After the Pending Order is approved, the User can create an Order from the approved Pending Order. |
- Administrators can use Tools to manage Users; Enable, Disable or Reset Password
- Reset passwords will be emailed to the user's Email Address.
Add User
Add new User details
Save progress using the "Save button
Note: After a User is created, Admins can directly manage a User's Quote and Order History using the Manage buttons.
Edit User
Edit User details
Save progress using the "Save” button
Delete User
Delete the User Details
The page reloads with a confirmation message.
The account is deleted.
Note: Once this action is performed, the user will be deleted completely from the system.