-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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.
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
Add a customer service role #3404
Comments
I've been handling similar permissions work on my main project, and can probably submit something for this if you want to assign it. |
This would be great. Go ahead
|
I like the idea. Also, I'm tempted to propose moving the user roles extension into core, what do you think? |
Thought about the same and tend to agree.
|
I think adding that extension would be great. It would have been really useful for the role and permission customizations I have going in my project. |
sounds good 👍 |
We are currently doing work on this as we implemented user roles this past month and are testing it now live with our CS team. We also have a handful of other customization outside of a vanilla install which come into play when considering this such as minor gems like solidusio-contrib/solidus_comments. Think we would need to discuss the current state of the extension and potential improvements which should be considered before discussing rolling it into core. We can provide some documentation and examples of how we have it implemented and pain points |
Hope this will release soon cause I can't bundle this solidus_user_roles anymore, the latest build in master branch is error. |
I'm fixing some bugs and I've opened some PRs to give compatibility with Solidus v3 to the |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
While discussing #3394 we cam up with the idea to add a "customer service" role. This should help us test the various permissions we are having and provide stores with a role that is not allowed to make critical changes like:
and many more
The text was updated successfully, but these errors were encountered: