Access with clear boundaries
Role-based authorization scopes workspace operations to the Client and authorized Sites. Customer administration and Platform Admin operations have separate permissions.
Security controls support the way your team manages models, configures Sites, and publishes product experiences.
Role-based authorization scopes workspace operations to the Client and authorized Sites. Customer administration and Platform Admin operations have separate permissions.
The server derives asset paths from trusted Site records. Browser input cannot select another Client’s asset prefix. Source models and processed outputs have distinct file capabilities.
Authorized uploads and downloads use short-lived signed access. Operational credentials remain on the server, and database operations run through a private backend.
Trusted viewer configuration binds each hostname to its Site’s model prefix. Browser query parameters cannot override that mapping. Embed restrictions complement these routing boundaries.
Viewer publication, certificate readiness, and DNS are checked separately. Platform Admin activation requires the Site’s agreement, assets, viewer, domain, and billing readiness.
Material onboarding and technical actions record the actor, Site, result, and time. Publishing uses concurrency protection to preserve other Sites’ configuration.
Published product viewers are intended for website visitors. Viewer routing and embed controls do not constitute visitor authentication or private product entitlements. Access to the management workspace and its file operations remains separately authorized.