Mark Posted July 31, 2019 Share Posted July 31, 2019 Hi Is anyone able to provide an idea of time involved in modifying the permissions structure so that as well as View, Edit, Add, Delete there was the same permissions again but just for those the user created.ie View Own, Edit Own, Add Own, Delete Own. For example, Once the user has added their own products, they can then only see and edit, delete, etc, those they created. Link to comment Share on other sites More sharing options...
datakick Posted July 31, 2019 Share Posted July 31, 2019 There is no record ownership in thirtybees, so it's not possible to implement record-level restrictions. Everything would have to be custom. Now, what records would you need to manage? Is it only products, or do you need this ownership on other records as well? Link to comment Share on other sites More sharing options...
Mark Posted July 31, 2019 Author Share Posted July 31, 2019 At this stage just envisaging for products only. Link to comment Share on other sites More sharing options...
dynambee Posted August 1, 2019 Share Posted August 1, 2019 There are modules for PS that enable this sort of functionality. This one, for example but there are others. You might want to contact the authors and inquire about if they would be willing to help with TB compatibility. Even at 120 Euro for the module it will be far cheaper than trying to build a custom solution. Link to comment Share on other sites More sharing options...
datakick Posted August 1, 2019 Share Posted August 1, 2019 It really depends on on the use case. If @Mark wants to implement multi-seller marketplace, then there are definitely modules for that. But if he wants to manage his employees access in back office (employee 'A' can view and edit all products, employee B can edit products in category Cars only,...) then it's totally different problem. And this one's very hard to implement. Link to comment Share on other sites More sharing options...
dynambee Posted August 1, 2019 Share Posted August 1, 2019 31 minutes ago, datakick said: It really depends on on the use case. If @Mark wants to implement multi-seller marketplace, then there are definitely modules for that. But if he wants to manage his employees access in back office (employee 'A' can view and edit all products, employee B can edit products in category Cars only,...) then it's totally different problem. And this one's very hard to implement. I think for that sort of usage scenario it would be better to have separate software to manage the products and have that software do listing updates via the API. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now