Functionality that allows you to grant permissions and assign them to specific roles.
See the entire graph with areas >>click<<
Right
Client area:
Customers |
|
Customer view |
|
Basic client edition |
|
Customer edition management (Advanced data, Additional data, Settings) |
|
Customer export |
|
Editing the due date (The financial data) |
|
Edit lock (The financial data) |
|
Trade credit edit (The financial data) |
|
Adding a client |
|
Deleting clients |
|
Editing the payer |
|
Edit lock |
|
Logical operator |
|
Trade credit edit |
|
Logical operator |
|
Customers | Conditions | Merchant limit | Logical operator |
|
Term payment | Logical operator | |||
Account lockout | Logical operator |
orderpath area:
Shopping path | With the selected Shopping Path, the conditions that are available in the orderpath do not work. The purchase path is full permission - admin, without conditions. If conditions are to be defined, do not set Shopping path, but more detailed permissions. |
Order view | Conditions like "Offer Approval" |
Warehouse changes | Conditions like "Offer Approval" |
Submit your order | Conditions like "Offer Approval" |
Offer view | Conditions like "Offer Approval" |
Transferring the offer to an external system |
It allows you to transfer the offer to an external system. Another permission is required to send the order, i.e. "Place an order". |
Creating an offer | Condition - Customer Branch
|
Offer approval | Conditions |
Total margin percentage
|
Logical operator |
|
Product line margin percentage
|
||||
Total net worth | ||||
Total gross value | ||||
Context storage |
|
|||
Bonus level | contains + value | |||
The minimum price of the product line | equal + value | |||
Creating an offer |
1. Adding a new right to create an offer by a given operator. - Remember that assigning the "shopping path" action allows you to perform any action in the orderpath area. - Authorization to create an offer should be placed in separate tiles Area: Orderpath, Actions: Create an offer
If we want to assign the orderpath area to the operator, actions should also be assigned. If the action is Offer:Create, this allows him to create an offer. The entitlement is checked after clicking the "New offer" button and when changing the basket to an offer. BE sends a 401 message with the following information: {"message":"Operator is not authorized to perform an action on a resource","requestId":"58567688-7249-4721-9ce6-6b380783a570","errorCode":"orderpath-autoconfigure-access-denied","error":true} At this point, the front-end will present a message with information about the lack of permissions.
2. Added a condition for the possibility of creating offers for customers only from specific branches. You can assign the following condition to the action: orderpath:Create: {OPERATOR_DEFAULT}, which will mean: you can create an offer only for customers who are assigned to your branch. Assigning a branch to an operator can be checked in its edition, in the company tab. In the condition, you can also specify the branch id (a long number from the operator's JSON) and assign them as well. An attempt to create an offer for a customer from a branch other than the operator's branch will also result in a 401 error
3. No assigned branch on the operator. In the absence of an assigned branch on a given operator, it is assumed that the condition is met. Such an operator can always create an offer. If the rights will be used, remember that operators must have assigned branches. For example, a sales director does not have to have an assigned branch - he can then assign an offer for a customer from each branch. |
|||
Conditions like "Purchasing path" The set Purchasing path permission gives the Admin permission in Orderpath, when set, the set conditions, e.g. to accept the offer, will not apply. |
Offer view |
1. I can add an offer 2. I can't accept - message "offer not found" |
Offer view + Offer approval |
1. I can add an offer 2. I can accept the offer - message "offer submitted" (and the status is "approved") |
Authorization to create offers by merchants.
In the configuration, you can add a permission that allows you to create offers. The operator to whom it will be assigned can create a new offer for the selected customer. However, if it is not assigned to the operator, he will not be able to create new offers.
Creating a new permission:
Go to Configurations -> Company -> Roles -> New Role
- In the area field, select "orderpath" -> in the action field: Create an offer
After assigning the action, you can create a new role. The role should be assigned to a merchant who can create offers in the ONe system.
If a given operator does not have a specific right, then when trying to create or copy an offer, the following message will be displayed: "You are not authorized to perform the action". - Extending the right to create offers for a specific customer branch.
Added according to pt. 1. the authorization may be extended to include branch information. In this case, it will be possible to create offers for customers from a specific branch.
To do this, you need to configure according to point 1. permission to add a new condition: "Customer Branch". The condition will be met when the condition is assigned according to the following scheme:
Customer branch -> equal -> {OPERATOR_DEFAULT}
{OPERATOR_DEFAULT} – means that an operator with the assigned right can create offers only for customers from his branch. Branch information will be taken from the context of the operator.
In the value field, you can also provide information about the "branchID", i.e. the ID of a given branch. The permission assigned in this way will allow you to create offers for customers with the same branch ID.
If a given operator does not have a specific entitlement, then when an attempt is made to create or copy an offer to a client from a branch other than the one assigned in the entitlement, the following message will be displayed: "You are not authorized to perform the action".
Settings area:
Settings is the area that is mainly responsible for managing the backoffice configuration and customer segments. Remember that the settings will work after the previous addition of permissions from the client "clients" area | Settings |
|
|
|
|
|
|
|
|
|
Authserver area:
Users |
1. I have a preview of users on the platform 2. I can recover the user's password 3. I can see my tasks and co-workers 4. I can add tasks 5. If I only add this permission, I will have all the permissions below 6. I have access to sales from any level of these settings |
User edit | 1. Makes you only delete the user |
User view | 1. I see users |
Creating a user | 1. If I add the "view clients" permission from the Client tab, I will be able to create a user |
Deleting a user | 1. Makes you only delete the user |
CMS area
Giving this permission means that the user will have access to the entire CMS tab on the backoffice.
pricing area:
This area applies to price, campaign, and view permissions.
Prices | Campaign activation | Campaign edit | Coupons view | Campaign view | Campaign creation | Editing coupons | Coupon submission | Campaign deactivation | Create a coupon |
Configuration examples:
Prices | He gets permission to view the campaign and the entire "promotions" panel - he gets permission - all regarding coupons |
Prices + Campaign activation + Campaign editing |
Gets permission to view the campaign and the entire "promotions" panel I can activate the campaign I see a button to edit the campaign |
Prices + Campaign activation |
Gets permission to view the campaign and the entire "promotions" panel I can activate the campaign |
Coupons view + Campaign view + Campaign creation + Coupon submission + Coupon editing + Campaign deactivation + Coupon creation | Bag - The selected permissions do not work properly, without adding the "price" permission, we do not have a promotions panel and the "price" permission automatically gives all the selected permissions |
invoice area:
Invoices | The operator receives a full preview of invoices in the sales tab |
Invoice view | The operator sees customer invoices |
Additional ONe configurations
1. Minimum prices for products on offers
i.e. the possibility of setting a minimum price for products. The new feature allows customers to set minimum prices for their products in up to 10 levels, which means that one product can have up to 10 different minimum prices. In this article, we will discuss in more detail how this new feature works and what benefits it can bring to ONe users.
Customers can set floor prices for their products in up to 10 levels. This means that one product can have up to 10 different floor prices.This functionality only works on offersand minimum prices and their levels must be entered through the integration API.
The next step in the rights is the ability to configure settings for a specific minimum price level that applies to the selected role of the operator. This means that a Merchant with the appropriate permissions will not be able to set the price of a product below the minimum price that applies to its level.
For example, if we have a product X with two levels of minimum prices (PLN 20 and PLN 30), the first operator has a minimum price level of PLN 20 set in the rights, he will not be able to set the price of this product below PLN 20 on the offer. However, the second operator with the rights for the minimum price level of PLN 30 will not be able to set the product price below PLN 30 on the offer.
Creating a new role and assigning it to an operator (salesperson)
- From the left menu, select "Configurations",
- Select "Company" from the left menu
- Go to the "Roles" tab,
- Press the "New Role" button,
- Enter role name in input,
- Press the "Create" button,
- Press the "Add permission" button,
- From the "Area" list, select "orderpath"
- From the "Actions" list, select "Offer view"
- Press the "Add permission" button
- From the "Area" list, select "orderpath"(Note that there must be two separate orderpath areas)
- From the "Actions" list, select "Offer Approval"
- Press the "Add/edit conditions to action" button in the line of the previously added action
- From the "Condition" list, select the "Minimum product line price" option
- In the "Value" field, select the level of the minimum price that will apply to the offer
- Click the "Update" button
- Press the "Add permission" button
- From the "Area" list, select "clients"
- From the "Actions" list, select "Client View"
- Press the "Update" button
What will be the result of the following actions?
After adding a product to the offer, the operator can edit the price of the product. If we have set the minimum price for this product to PLN 30 and the Merchant wants to set PLN 25, it will be highlighted in green and in the basket he will not be able to process the order. The merchant will receive the following message.
Link to API documentation and instructions on how to add price levels >>CLICK<<
2. Bonuses for individual products
What is the business purpose of introducing bonuses?
The simplest example: When you sell X products of this manufacturer, after exceeding the limit of units sold, sell your products cheaper, you as a distributor of this manufacturer can then charge yourself higher margins/sell these products cheaper.
- A new endpoint has been created in the integration API in the Price Helper microservice, which allows you to add bonus levels for a specific product.
Instructions and explanations on how to add bonuses via the API >>CLICK<<
- The administrator in the backoffice has the option of assigning the bonus level to the role of the operator from the trader's panel. More than one bonus level can be assigned to one operator.
- At the price editing modal level, it is possible to expand information about the bonus on the offer. The information that is visible is the percentage of the bonus along with the purchase price calculated on its basis and the margin including the bonus, calculated on the basis of the commission factor.
- This factor is one for each client platform and can be configured in Settings > Price helper > Trade commission factor / trade_margin
What is the trading commission factor?
The commission factor is the extra compensation that traders get for selling products. The value of this factor is determined in the system settings, where in the general configuration, in the orderpath section, a decimal value can be set. The default value is 1, which means that the commission is not included in the calculations. If we want the values in the offer to be reduced by the commission factor, then this value must be lower than 1, e.g. 0.8. This will allow you to observe whether, despite taking into account the commission factor, the margin on the product is still appropriate and whether it can be offered to the client. It is worth noting that the margin displayed on the product line is multiplied by the trade margin factor, which can also be set in the configuration.
Comments
0 comments
Please sign in to leave a comment.