Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update company-user-roles-and-permissions-overview.md #2889

Closed
wants to merge 1 commit into from
Closed

Update company-user-roles-and-permissions-overview.md #2889

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions ...company-account-feature-overview/company-user-roles-and-permissions-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,22 +96,22 @@ These values are referred to as *Company Role Permissions*.

{% endinfo_block %}

Permission can also be *Yves-side* and *Zed-side*.
Permission can also be *Storefront-side* and *Backoffice-side*.

* Yves permissions do not need to get any data from the database. They refer to key-value storage or search to check the right for actions.
* Storefront permissions do not need to get any data from the database. They refer to key-value storage or search to check the right for actions.

{% info_block infoBox %}

For example, the permission to view a product, page, or permission to place an order, permission to place an order with grand total less than X would be Yves-side permissions.
For example, the permission to view a product, page, or permission to place an order, permission to place an order with grand total less than X would be Storefront-side permissions.

{% endinfo_block %}

* Permissions that require some data from the database or additional business logic on top to check the rights for actions are referred to as Zed permissions.
* Permissions that require some data from the database or additional business logic on top to check the rights for actions are referred to as Backoffice permissions.

{% info_block infoBox %}

For example, the permission to add to cart up to X [order value] is a Zed-side permission. In this case, the process of permissions check is as follows:
1. After the user clicks **Add to cart**, the request comes to Zed, and the prechecks are made following the "add to cart" request.
For example, the permission to add to cart up to X [order value] is a Backoffice-side permission. In this case, the process of permissions check is as follows:
1. After the user clicks **Add to cart**, the request comes to Backoffice, and the prechecks are made following the "add to cart" request.
2. Then, the calculations are run. The calculations apply discounts per items, and then per cart (total). The logic behind this is simple: a user might have a discount for a specific item and a discount for an order starting from a specific order value. The order value is calculated taking the discount per items into account, and therefore the discount per cart is applied after all discounts per items have been calculated.
3. After the calculations have been made, the cart is saved.

Expand Down
Loading