Create workspace material rules
Map stable source-material names to approved Glossi materials, then verify the result on representative products.
Workspace material rules preserve known finish logic. A rule can match a source material group by name and associate it with an approved material from the workspace library.
The rules and their management interface are shipped. Execution through every automation, API, and direct-colorway path is not complete. Verify where a rule is applied before using it as unattended production logic.
Build a rule
Each rule contains:
- Match text: The source group name or partial name to find.
- Match mode: Contains for a broader match or Exact for one full name.
- Replacement material: The approved workspace material associated with that match.
- Open Settings, then Workspace.
- Find Material Swaps.
- Add or manage rules.
- Enter the match text and choose the match mode.
- Select the replacement material.
- Order the rules from most specific to most general.
- Save.
Design names for repeatability
Rules are useful only when source naming is stable. Upper Leather and upper_leather can be normalized by supported matching behavior, but Material.003 does not communicate a reusable product region.
Use Exact for a controlled source contract. Use Contains when a meaningful family of names should receive the same finish.
Resolve competing matches
Rules are evaluated by priority. When two rules can match the same group, the earlier rule wins. Put narrow exceptions before broad defaults.
A saved project calibration can take precedence over a workspace default. Confirm the final material in Studio rather than assuming the rule was the last instruction applied.
Validate the rule
Test at least one model from each intended product family:
- confirm the correct groups matched
- inspect regions that should not change
- verify texture scale and orientation
- inspect transparency, metal, and glass separately
- save the project only after the intended material is visible
For automation use, validate the entire run through rendering and delivery. Do not rely on the presence of a Material Swap node as proof that direct execution is complete for the workspace.