.png){kind=small}
Role-based access for countertop shop teams
SlabOS roles distinguish the work a user can perform from the information a shop chooses to show. This matters across estimating, pricing, inventory, financial records and communication. The public MCP page adds a related principle for owner-connected AI: access should be evaluated in the context of the authenticated user and supported actions.
Inputs this workflow uses
User responsibilities, assigned roles and applicable account restrictions.
Outputs to evaluate
Access appropriate to the user's permitted work.
A representative demonstration
Compare a synthetic estimator and crew account performing their respective tasks, including an action each should not be able to perform.
Bring a representative job to a SlabOS demo and see how this capability fits your shop’s work.
Scope and availability
A hidden button is not proof of authorization enforcement. Access claims require server-side checks of allowed and denied actions.
Product context and useful resources
- Features
Place this capability within SlabOS estimating, production, inventory and office work.
- Pricing
Review the published commercial model and what is included; confirm current terms for your shop.
- MCP for owners
Review the public scope and boundaries of connecting an owner-selected AI to SlabOS.