Product configurator security

Clear access. Controlled product data.

Your configurator connects product knowledge, buyers and business systems. Define who can see and change each record, what reaches the browser and which evidence your implementation must provide.

Discuss your requirements

Four workflows. Explicit access boundaries.

Public configurator

Website visitor or invited customer

Dealer workspace

Dealer, distributor, showroom or external sales partner

Internal operations

Sales, product, pricing, operations and administrators

Integration service

CRM, ERP, PIM, ecommerce, document, pricing or analytics service

Define access for each workflow.

Explore the requirements for public visitors, dealers, internal teams and integrations. Agree the identity, records, actions and evidence for each surface before implementation.

Public configurator

Audience
Website visitor or invited customer
Purpose
Explore valid products, save a project and request a quote without exposing private catalogue or account data.
Identity requirements
Anonymous session, signed project link or customer identity—selected by the journey and risk model.
Lifecycle
Define session, draft-project and shared-link lifetime separately.
Downstream handoff
Lead or project event to the accepted CRM, quote or workflow endpoint.

Data in scope

  • Published product options
  • Public price result if enabled
  • Customer-entered project details
  • Consent and attribution data

Actions to govern

  • Configure
  • Save
  • Request quote
  • Open permitted shared project

Boundaries to enforce

  • No unpublished products
  • No dealer price lists
  • No other customer projects
  • No administrative fields

Evidence to request

Anonymous-access test, project-link expiry test, response-field inspection and cross-project authorization test.

Notes remain in this page’s memory until reset or navigation. The download includes your selected workflow, questions and notes. They are not copied into the enquiry form.

Twelve control domains to agree.

Data inventory and classification

What enters the system, why, and how sensitive is it?

Map customer contact details, addresses, site photos, product selections, prices, discounts, drawings, documents, model assets, analytics identifiers and integration payloads. Classify each field before choosing storage, access, retention and export rules.

Evidence to request

Field-level data map with purpose, owner, sensitivity, location, recipients and retention.

Identity and authentication

Who or what is making the request?

Separate anonymous visitors, invited customers, dealer users, workforce users, administrators and machine identities. Define sign-in, federation, stronger authentication, recovery, invitation, service credentials and deprovisioning according to risk.

Evidence to request

Identity journeys, authentication policy, recovery test and joiner-mover-leaver test.

Authorization and tenant isolation

May this identity perform this action on this exact object?

Check role, account, project, object, action, market and environment on the server. A user who may view one quote must not automatically view another; an administrator action must not be inferred from a hidden button.

Evidence to request

Positive and negative object-level tests across roles, accounts, records and endpoints.

Browser and 3D asset exposure

Which product knowledge reaches the customer device?

A web configurator necessarily sends visual and interaction data to a browser. Decide whether geometry, textures, option IDs, pricing inputs, rule metadata or document links are public, transformed, signed, time-limited or kept server-side.

Evidence to request

Network-response inspection and asset-access test performed as an unauthenticated visitor.

API and webhook security

Can integrations exchange data without widening access?

Protect every object and function, validate payloads, limit resource use, verify webhook origin, reject replay where required, keep an API inventory, control versions and treat third-party responses as untrusted input.

Evidence to request

Contract tests for identity, object access, schema, signature, replay, rate, timeout and retry behavior.

Secrets and environment separation

Where do credentials live and who can use them?

Keep service credentials, signing keys and administrative secrets out of browser bundles, repositories and documents. Separate development, test and production responsibilities, rotate credentials and verify revocation.

Evidence to request

Secret inventory, access list, rotation record, client-bundle scan and revoked-secret test.

Logging and auditability

Can the organisation reconstruct security and business-critical events?

Capture who or what acted, the target, action, result, time, tenant, correlation identifier and relevant revision. Keep security events distinct from business analytics and avoid placing credentials or unnecessary personal data in logs.

Evidence to request

Event catalogue, sample records, access controls, retention, alert path and investigation exercise.

Privacy lifecycle

How is personal data minimized, retained, corrected, exported and deleted?

Connect each personal-data field to a purpose and lifecycle. Define controller and processor responsibilities, subprocessors, data-subject handling, regional transfer needs, backups and the effect of deletion on quotes, orders and legal records.

Evidence to request

Processing record, DPA responsibilities, retention schedule and completed access/deletion scenario.

Availability, backup and recovery

What happens when a dependency or region is unavailable?

Define recovery objectives from the business process, not from a generic uptime slogan. Test backup restoration, degraded journeys, queued integrations, idempotent retry and reconciliation after service returns.

Evidence to request

Recovery objectives, restore result, dependency-failure test and reconciled record sample.

Secure change and vulnerability handling

How are risks prevented and corrected after launch?

Security is a release process. Define dependency and code scanning, review gates, vulnerability intake, severity, remediation targets, emergency change, environment promotion and retesting of affected access and data flows.

Evidence to request

Change record, scan result, remediation workflow and regression evidence linked to a release.

Incident readiness

Who decides, contains, communicates and learns?

Name the operational contacts and evidence sources before an incident. Cover account compromise, cross-tenant exposure, malicious files, credential leakage, abusive automation, integration compromise and incorrect public publishing.

Evidence to request

Incident roles, contact path, severity model, tabletop result and corrective-action record.

Supplier and subprocessor governance

Which external service receives or protects the data?

Inventory hosting, authentication, email, storage, analytics, support and integration providers. Record their role, data, region, contract, access, dependency, change-notification route and exit plan.

Evidence to request

Current supplier register, subprocessor list, responsibility boundary and offboarding test.

Classify data before choosing controls.

Published product data
Fields to inventory
Public names, finishes, options, thumbnails and allowed product descriptions.
Decision to document
May be intentionally public, but draft and withdrawn revisions still need publishing controls.
Commercial product data
Fields to inventory
Costs, margins, dealer price lists, discount ceilings, account terms and internal price formulas.
Decision to document
Restrict by role and account; return only the commercial result needed by the current journey.
Customer and site data
Fields to inventory
Name, contact details, address, site dimensions, photos, notes and appointment information.
Decision to document
Minimize collection, state purpose, control access and connect retention to the business record.
Project and quote data
Fields to inventory
Saved configuration, revisions, price results, documents, approvals, deposits and status history.
Decision to document
Protect object-level access and preserve enough revision context to explain the accepted transaction.
Operational and production data
Fields to inventory
BOM, cut values, drawings, surveys, installation files, ERP identifiers and delivery status.
Decision to document
Limit to accepted operational roles and verify the exact revision delivered downstream.
Security and technical data
Fields to inventory
Credentials, tokens, logs, environment details, errors, dependency versions and security findings.
Decision to document
Separate secrets from observable records; restrict logs and findings while keeping them useful for response.

Define the role and object scope.

Use these responsibilities as a starting point for your own role matrix. Agree every permission and exception, then test enforcement on the server for the exact object, account and action. A role name alone does not grant access.

Website visitor
Catalogue
Published catalogue
Projects
Own draft or signed link
Price context
Public result
Discount
No
Publishing
No
Customer
Catalogue
Published catalogue
Projects
Own invited projects
Price context
Own permitted quote
Discount
No
Publishing
No
Dealer salesperson
Catalogue
Account catalogue
Projects
Account projects
Price context
Account price context
Discount
Limited
Publishing
No
Sales manager
Catalogue
Assigned markets
Projects
Team projects
Price context
Approved price context
Discount
Approve
Publishing
No
Product manager
Catalogue
Draft + published
Projects
Review samples
Price context
Rule test context
Discount
No
Publishing
Prepare
Platform administrator
Catalogue
As authorised
Projects
As authorised
Price context
As authorised
Discount
No
Publishing
Publish/rollback
Integration service
Catalogue
Contracted fields
Projects
Event object only
Price context
Contracted result
Discount
No
Publishing
No

Review the ways a workflow can fail.

Project identifier substitution
Risk to test
A signed-in user changes a project or quote ID and receives another customer or dealer record.
Control to verify
Enforce object-level authorization for every read, update, export and document request; test IDs from another account.
Price and rule data overexposure
Risk to test
The public client receives internal costs, margins, unpublished rules or dealer-only price lists that the interface merely hides.
Control to verify
Design response schemas for the current audience and inspect actual browser traffic, not only visible screens.
Cross-tenant dealer access
Risk to test
A dealer user searches, exports or opens projects belonging to another dealer, branch or brand.
Control to verify
Apply account scope server-side to queries, files, exports, analytics and integrations; include negative tenant tests.
Abusive configuration or quote automation
Risk to test
Automated requests consume rendering, document, email, storage or pricing resources and interrupt legitimate buyers.
Control to verify
Set business-aware rate, concurrency, payload and cost limits; monitor unusual patterns and protect sensitive flows.
Webhook forgery or replay
Risk to test
An untrusted request marks a quote accepted, creates an order or repeats an earlier event.
Control to verify
Authenticate origin, validate signatures and timestamps, enforce idempotency and reconcile the resulting state.
Stale or overbroad shared links
Risk to test
A forwarded quote or project link remains valid beyond its purpose or exposes editing and private fields.
Control to verify
Scope the link to an object and action, define expiry and revocation, and test anonymous access after status changes.
Unsafe customer uploads
Risk to test
Site photos, drawings or attachments are used to deliver malicious files, unexpected content or excessive storage load.
Control to verify
Validate type and size, isolate storage and delivery, control access, scan where required and never trust the filename alone.
Privileged publishing mistake
Risk to test
Draft prices, products, assets or rules are published to the wrong market, brand or dealer network.
Control to verify
Separate preparation from approval where risk warrants it; preview scope, log the change and support controlled rollback.

Turn requirements into acceptance evidence.

Cross-object access

Use a valid user and request a project, quote, document and export owned by another permitted test account. Every route must deny access without leaking record content.

Cross-tenant search

Search, filter, count and export from one dealer account using identifiers known to exist in another account. Results and totals must remain isolated.

Role downgrade

Remove discount, export or publishing permission from an active user. The next protected action must follow the new policy, including direct API requests.

User deprovisioning

Disable a workforce or partner identity. Test active sessions, refresh, invitations, API access and ownership transfer according to the accepted policy.

Public response inspection

Inspect page source, network payloads, 3D assets, files and error responses as an anonymous visitor. Confirm private product and price fields are absent.

Shared-link lifecycle

Open a valid shared project, then test expiration, revocation, quote acceptance, project revision and forwarding to a different browser.

Webhook integrity

Send an unsigned, wrongly signed, expired, replayed, reordered and duplicated event. Verify rejection or idempotent handling and attributable logs.

Resource limits

Exercise accepted maximum dimensions, option counts, file sizes, quote requests, exports and concurrent calculations. Verify stable errors and protected service availability.

Log reconstruction

Perform sign-in, denied access, price approval, export and publishing actions. Reconstruct who, what, when, object, tenant, result and correlation without exposing secrets.

Retention and deletion

Expire a test lead and complete the approved deletion or anonymization flow across the primary record, searchable views, files, integrations and documented backup behavior.

Backup restoration

Restore a representative catalogue, configuration and project set. Verify object identity, access policy, files, revisions and downstream reconciliation—not only database startup.

Dependency failure

Interrupt one agreed external service. Confirm the intended degraded journey, queued or failed state, alerts, safe retry and reconciliation after recovery.

Twenty questions for your supplier review.

Data and responsibilities
  • Which data fields enter the configurator, from which source, for which purpose and in which region?
  • Which party is controller or processor for each customer, dealer, workforce and analytics journey?
  • Which product, price, rule, model and document data reaches the browser or a public asset URL?
  • Which personal-data fields are optional, required, exported, corrected, anonymized or deleted?
Identity and access
  • How are public, customer, dealer, workforce, administrator and machine identities separated?
  • Where is authorization enforced for projects, quotes, files, price lists, exports and administrative functions?
  • How is tenant or account scope applied to searches, counts, analytics, documents and downstream events?
  • Which authentication, federation, stronger-authentication and recovery options apply to each role?
APIs, credentials and uploads
  • How are API objects, functions, fields, payload sizes, rates, versions and external responses controlled?
  • How are webhooks authenticated, replay-protected, retried and reconciled?
  • Where are credentials stored, how are environments separated, and how are secrets rotated and revoked?
  • How are customer uploads validated, scanned, stored, served and removed?
Operational governance
  • Which security and privileged business events are logged, protected, monitored and retained?
  • Which subprocessors receive data, in which regions, under which responsibility and change process?
  • What are the accepted backup, recovery, availability and dependency-failure objectives?
  • How are vulnerabilities reported, prioritized, corrected, communicated and retested?
  • Which security checks run before a catalogue, rule, pricing, integration or platform release?
  • How are security incidents classified, investigated, communicated and connected to corrective action?
Evidence and ownership
  • What evidence is supplied at acceptance and on an agreed recurring cadence?
  • Who owns every open exception, compensating control, deadline and risk acceptance?

Agree a security-event field contract.

Specify the fields needed to reconstruct a protected action. Link records to the relevant policy and revision, protect access and retention, and exclude credentials and unnecessary personal data.

eventId
Unique event reference; define duplicate handling and integrity requirements.
occurredAt
Actual event time with timezone; document clock synchronization and processing delay.
environment
The actual controlled environment in which the action occurred.
tenantId
Account or tenant scope where applicable; do not use a display name as the security boundary.
actor
Attributable user or service identity and relevant role context, with restricted access to personal data.
action
Controlled business or security action identifier, independent of button wording.
target
Exact record type, identifier and revision needed to reconstruct the action.
result
Actual allowed, denied or failed outcome with a controlled reason code where needed.
policy
The applicable authorization or approval policy version.
correlationId
Reference joining the request, protected action and downstream delivery without copying secrets.

Custom software for manufacturers

Connect complex products to controlled business workflows.

We specialise in complex products. Configurix builds custom configurators and business or factory software for your catalogue and workflow: lead qualification and CRM, appointments and calendars, prices and quotes, materials and BOM, orders, jobs and invoicing. We scope permissions, data ownership and integration responsibilities around the actual people, products and systems involved.

CRM and qualified leads

Capture the selected product, dimensions and options with each enquiry. Qualify by product fit, project requirements and commercial readiness, then assign the next action to the right salesperson.

Configurix workspaceQuote revision

New enquiry

Product configurator security

Product fit

Qualified

Product configurator security

Requirements

Proposal

Product configurator security

Next action

Calendars and appointments

Let a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.

Configurix workspaceQuote revision
  • 09:00Project review
  • 11:30Technical review
  • 14:00Production planning

Bill of materials and factory data

Map product selections to component codes, quantities, materials and cut lengths. Build the sales or manufacturing BOM your team needs, with revisions and production review rules defined for your products.

Configurix workspaceQuote revision
Bill of materials and factory data
ComponentQuantity
FRM-01Configured components1
PNL-02Materials and quantities1
KIT-03Agreed operations1

Mapped to your product codes

Live prices and branded quotes

Apply your own formulas, price lists, dealer margins and approval rules. Generate a quote containing the saved specification, product images, commercial terms and a clear customer approval step.

Configurix workspaceQuote revision

Quote revision

Your catalogue
Options
Services
Your price rulesBranded PDF

Orders, jobs and production

Carry accepted choices into order lines and assigned jobs. Keep product revisions, required approvals, documents and delivery tasks together so sales and the factory work from the same specification.

Configurix workspaceQuote revision
  1. Accepted quote01
  2. Configured order02
  3. Production job03
  4. Installation04

Invoicing and accounting

Connect accepted orders to deposits, invoice drafts, payment terms and your accounting workflow. Agree which system issues the invoice and how references and confirmed payment status return to the project.

Configurix workspaceQuote revision
Draft invoice

Product configurator security

Order referenceProduct configurator security
Customer—
Payment terms—
Accounting handoff

Built for your website. Connected to your systems.

Launch a branded configurator in your existing website or a custom sales portal. Connect CRM, ERP, PIM, ecommerce, calendars and accounting through available APIs, webhooks or agreed imports. We define the data, permissions and responsibilities for each connection with your team.

  1. 01Your website
  2. 02Configurator
  3. 03CRM & calendar
  4. 04ERP & accounting

Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.

Discuss your requirements

Product configurator security questions

Scope security around your product workflow.

Tell us about your catalogue, audiences and current systems. We can define a custom configurator and software workflow with explicit access boundaries, integration responsibilities and acceptance evidence.

Book a demo

Step 1 of 2 — your details, then pick a time.

2 min

By submitting you agree to be contacted about Configurix. We respect your privacy.