We actually read these.
Ideas submitted here go to the product team, not into a void. Add yours, vote on others, and comment on what matters to your business.
Talk to our Product Managers live: every other Monday, 1:00–2:00 PM ET → https://www.d-tools.com/cloud-product-office-hours
At the moment, it seems impossible to restrict SKU creation without also removing access to the D-Tools Product Library.
In our workflow, Sales staff need access to the Product Library, but they should not be allowed to create new SKUs. SKU creation must be restricted to the Operations team.
Could these permissions be separated so that Sales can access the D-Tools Library without being able to create new SKUs?
Thanks!
Hi @Guest Thanks for the feedback! Before we scope this out, I want to make sure I understand exactly what your Sales team needs, since there are a couple of different scenarios here:
Today, if you remove the "Create and Edit Catalog Item" permission from your Sales users, they keep full access to your company catalog — they can browse it, search it, and add any of those products to quotes. What they lose is the D-Tools Library tab, because pulling a product from the D-Tools Library automatically adds it to your catalog as a new item (which is why it's tied to that permission).
So a couple of quick questions:
What should Sales be able to do with the D-Tools Library? Do they need to just browse/search it for reference (specs, pricing, etc.), or do they need to add library products to their quotes?
What does "creating a SKU" mean in your workflow? Is the concern specifically about Sales hand-creating custom items in the catalog, or does it also include adding products from the D-Tools Library (since that creates a catalog item too)?
If the goal is "Sales can only quote products that Operations has already approved into the catalog," that's actually supported today with the existing permissions. But if Sales needs to pull products from the D-Tools Library onto quotes without Operations reviewing them first, that would be a new capability, and understanding your workflow will help us design it right.
Thanks!