Group restriction

Hello
I want to create more group by brand. each group will have its own restrection (view product, view promotion).
my question is: how to affect the client in several groups?
can we adapt this logic?
Thank you.

Topic

[Andrey YatsenkoModerator]

Hi,

Are you talking about customer groups (for users at storefront) or user groups (for management console users?

[msalmi.kaisParticipant]

for users at storefront

[Andrey YatsenkoModerator]

Basically, you just need to create custom ACL voter if I understand right your question. Here is the doc How to use Voters.

But I can’t understand how did you configure permissions per customer group. As I see there is only role based permissions configuration. Do you automatically create roles for each new group or how did you manage this?

• This reply was modified 5 years, 11 months ago by  Andrey Yatsenko.

[seddik.dimassiParticipant]

THANKS ANDREY,

Actually, the problem is that our marketplace is selling products from different brands. We need to enable restriction on brands for clients (using groups or other method).
The best will be able to check or uncheck available brand’s product for every customer.
Do you think using groups will be the best solution?

[Andrey YatsenkoModerator]

Group can have many customers, but you want to configure it per customer.

So it’s better to have new relation form Customer to Brand, you can create it using schema migration as Customer is an extendable entity, let’s call new relation availableBrands, or you can create relation from the Brand side. Depending on your business logic choose what is better here.

Then you can just create regular ACL voter for the product entity, as an example you can see this one https://github.com/oroinc/orocommerce/blob/1.6/src/Oro/Bundle/VisibilityBundle/Acl/Voter/ProductVisibilityVoter.php

Your voter needs to get customerUser from token storage and then check if product.brand exists at customerUser.customer.availableBrands. That’s it.

[seddik.dimassiParticipant]

Thanks a lot ! Great – I think it ll be better to make it by customers @ Kais : What do you think?

[msalmi.kaisParticipant]

Hi,
@Andrey, can we apply this ACL voter for the frontend product by customers ?
i think this example https://github.com/oroinc/orocommerce/blob/1.6/src/Oro/Bundle/VisibilityBundle/Acl/Voter/ProductVisibilityVoter.php it’s for backend product.
there is a more detailed example to follow, or a course for voting acl?
Thank you Andrey for help.

[Andrey YatsenkoModerator]

What do you mean by frontend and backend products?

We use same entity on both UIs.

This listener used only on front-store according to this check and will be skipped on management console https://github.com/oroinc/orocommerce/blob/1.6/src/Oro/Bundle/VisibilityBundle/Acl/Voter/ProductVisibilityVoter.php#L38
In case of backend this will just return ACCESS_ABSTAIN, that means that voter doesn’t know how to vote on it.

As I mentioned above general documentation about voters can be found here How to use Voters.
I don’t know about any other docs.

[msalmi.kaisParticipant]

Thank you very much Andrey.

[Author]

Replies