Custom configurators and connected business software

Product configurator SSO. The right access for every team.

We specialize in complex products. Configurix builds custom configurators, dealer portals and business software with an access model for your customers, partners and employees, connected to your agreed identity provider.

Plan your integration
Configured project access

Trusted identity

Assigned permissions

Permitted project

Authentication, user provisioning and business permissions are separate responsibilities. Identity-provider support and the exact protocol profile are defined and verified for your deployment.

A product journey your team can continue.

Connect the sign-in journey

Define how employees, dealers or customers authenticate through the chosen identity provider. Evaluate the OpenID Connect or SAML profile, recovery and session behaviour your deployment needs.

Protect product and price access

Map users to approved accounts, catalogues, price lists and project permissions. Enforce access on the server for every protected record and action, as well as in the interface.

Manage the account lifecycle

Agree invitations, provisioning, role changes and offboarding with the responsible team. Test revoked access, account linking and administrator recovery against the working implementation.

Interactive identity architecture planner

Define users, federation, lifecycle and authorization together.

Choose the closest deployment. The result identifies the trust, mapping and acceptance evidence to prioritize. Actual provider capabilities, protocols, roles and security requirements depend on the working systems and signed Configurix scope.

Primary audience
Federation model
Account lifecycle
Authorization model

Custom software for manufacturers

A configurator up front. Your business connected behind it.

We specialize in complex, configurable and made-to-order products. We build custom software around your catalogue, calculations, permissions, sales process and factory workflows.

Connected software

Authentication, user provisioning and business permissions are separate responsibilities. Identity-provider support and the exact protocol profile are defined and verified for your deployment.

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

Configured project access

Product fit

Qualified

Configured project access

Requirements

Proposal

Configured project access

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

Configured project access

Order referenceConfigured project access
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.

Plan your integration

Your product. Your systems. A connected workflow.

Bring one complex product, your current systems and the result your team needs. We will define the configurator, custom software, responsibilities and acceptance checks together.

Tell us about your business

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.

Questions and answers

Technical integration guide

Identity architecture definition

SSO is one layer—not the complete access-control system.

Enterprise access becomes safer and easier to explain when authentication, federation, provisioning and authorization remain distinct. Each layer has different protocols, owners, failure modes and acceptance evidence.

Authentication

How a person or service proves its identity. SSO can delegate human authentication to a trusted identity provider.

Federation

How Configurix, as the relying party, verifies an assertion from an identity provider and establishes a local session.

Provisioning

How user accounts, group membership, activation, update and deactivation are managed across their lifecycle.

Authorization

What the authenticated identity may do to a specific tenant, project, price list, quote, order or administration object.

Trust and authority matrix

Put identity evidence and business permission at the correct boundary.

AuthorityPrimary responsibilityBoundary to prove
Identity providerPrimary workforce or partner authentication, authenticators, account status, group or attribute assertions and federation keysConfigurix validates the trusted issuer and assertion; it does not blindly trust an email address or unsigned browser field.
Configurix identity layerFederated account resolution, local user identity, session, tenant memberships, role mappings and identity audit eventsAuthentication establishes who signed in. Local policy still determines which Configurix resources are accessible.
Business tenant ownerDealer, distributor, showroom, brand, legal entity, market and product-assignment decisions by agreed workflowExternal IdP groups cannot grant access to another tenant unless the mapping and business authority explicitly allow it.
Product and pricing ownersCatalog, rule, price-list, discount, quote, document and publication permissionsPowerful product or pricing actions need explicit roles, object scopes, approval and audit—not a generic authenticated state.
Application APIsHuman-session APIs, service identities, scopes, object authorization, rate controls and integration auditA valid access token is not sufficient proof that its subject may read or change the requested project or tenant.
Connected CRM, ERP or ecommerceTheir own users, service accounts, object permissions and downstream business authorityDo not reuse a browser user's privileges as an uncontrolled integration identity or copy unnecessary identity attributes.

Canonical identity contract

Carry trusted identity without turning every claim into permission.

Federation establishes a trusted authentication context. Configurix should retain the smallest identity contract needed to resolve a user, create a session, map approved business membership and explain authorization decisions.

issuer

Exact trusted identity-provider identifier and configured federation connection

subject

Stable provider-scoped subject identifier used with the issuer to resolve the local account

audience

The intended Configurix client or relying-party identifier accepted for this assertion

assurance

Authentication time, method, context or agreed assurance information needed by policy

attributes

Minimum approved name, email, locale, organization or other claims with source and purpose

tenant

Configurix organization, dealer, region or brand membership established through controlled mapping

roles

Local role and capability assignment, plus who or what is authoritative for each change

lifecycle

Created, active, suspended, deactivated, removed and reactivated state with effective timing

session

Issued, refreshed, expired, reauthenticated, revoked and logged-out state by channel

audit

Correlation, actor, source, target object, decision, reason, timestamp and administrative evidence

Role model

Define business capabilities without weakening tenant and object isolation.

Customer

Create and resume owned projects, review allowed prices or quotes and approve or request action by scope.

Dealer user

Work only within assigned dealer accounts, catalogs, price lists, customers, projects and permitted commercial actions.

Dealer manager

Manage approved dealer users or assignments without crossing the manufacturer's tenant or global administration boundary.

Salesperson

Create and continue customer projects, prepare quotes and use permitted price or discount workflows.

Product manager

Maintain assigned catalog content, choices, rules, assets and releases through the accepted governance process.

Pricing manager

Maintain assigned price sources, discount policy, validity and approvals without inheriting unrelated system administration.

Operations user

Read accepted project, order, survey, installation or production context required for assigned operational work.

Administrator

Manage tenant configuration and authorized identities; sensitive global actions remain deliberately limited and audited.

A role is not a global data entitlement. Every protected request should also evaluate organization, ownership, product assignment, market, price authority, project sharing and other applicable object policy.

Federated identity lifecycle

Make trust, access and deactivation observable from end to end.

1

Establish trust

Register the exact IdP and Configurix identifiers, endpoints, redirect locations, keys, certificates and accepted profile.

2

Resolve organization

Determine the approved tenant, dealer, market or brand from a controlled connection or business mapping.

3

Authenticate

Send the user through the agreed federation flow and validate issuer, audience, signature, time and transaction protections.

4

Resolve account

Match the issuer-and-subject pair to one Configurix user; avoid treating mutable email alone as permanent identity.

5

Provision membership

Create or update approved local attributes, tenant membership, groups and status through JIT, SCIM or administration.

6

Authorize object

Evaluate role, tenant, ownership, product, price and project policy on every protected request.

7

Operate session

Apply expiry, refresh, reauthentication, logout, device and sensitive-action policy to the Configurix session.

8

Deactivate and reconcile

Remove access promptly, terminate or limit sessions by policy and compare IdP, SCIM and Configurix state.

Identity integration patterns

Match the access pattern to the people and systems using Configurix.

One workforce IdP

Employees use one managed identity provider for Configurix sales, product, pricing and administration roles.

Workforce IdP → OIDC or SAML → Configurix local account and role mapping

Control: Keep privileged roles explicit and test suspended users, group removal, old sessions and administrator recovery.

Manufacturer plus dealer federation

Internal users and external dealer organizations authenticate through different trusted identity connections.

Home-realm or tenant choice → approved IdP → dealer membership → object policy

Control: Bind each connection to approved organizations; never derive cross-tenant access from a user-entered domain alone.

SCIM-managed enterprise lifecycle

The organization requires centralized user and group creation, update, suspension and deprovisioning.

Identity lifecycle system → SCIM service → Configurix user, group and active-state reconciliation

Control: Define group-to-role mapping, soft versus hard deletion, reactivation, conflicts, retries and manual exception ownership.

Invited customer identity

Customers receive controlled access to specific configured projects without inheriting workforce identity policy.

Project invitation → customer authentication → project membership → scoped session

Control: Use expiring invitations, verified account resolution, project-level authorization and clear sharing revocation.

Step-up for sensitive actions

Price publication, high discount, user administration or order approval requires stronger or recent authentication.

Existing session → policy trigger → reauthentication or stronger context → authorized action

Control: Define which actions require step-up, what evidence is accepted, expiry and behavior when the IdP is unavailable.

Separate service identities

CRM, ERP, ecommerce, PIM or automation needs API access without impersonating a human browser user.

Integration identity → scoped credential or token → Configurix API → object authorization and audit

Control: Use least privilege, rotation, environment isolation, workload ownership and no interactive login privileges.

Session, logout and recovery

Define what happens after the identity provider says yes.

Federation creates a Configurix session; it does not manage every later session decision automatically. Expiry, refresh, reauthentication, logout, deactivation and recovery need explicit behavior and working evidence.

Session creation

Create a Configurix session only after complete assertion and transaction validation.

Idle and absolute expiry

Define both inactivity and maximum session age according to role and business risk.

Reauthentication

Require recent or stronger authentication for sensitive administrative or commercial actions when policy demands it.

Refresh and rotation

Protect and rotate refresh material according to the chosen protocol and application architecture.

Local and federated logout

Document what local logout, IdP logout, front-channel and back-channel behavior actually terminate.

Account deactivation

Decide whether existing sessions are revoked immediately, expire naturally or require a separate revocation event.

Recovery

Define break-glass and administrator recovery without creating a permanent bypass around enterprise identity policy.

Audit

Record sign-in, failure, mapping, role change, step-up, logout, revocation and privileged action evidence.

Implementation blueprint

Start with one identity provider and every role it can reach.

01

Inventory identities and journeys

List customer, dealer, sales, manager, product, pricing, administrator and service-account use cases.

02

Choose the federation profile

Document IdP, protocol, flow, client or service-provider identity, endpoints, keys, claims and logout expectations.

03

Define stable account resolution

Use issuer and subject identity, duplicate controls, migration rules and deliberate email-change behavior.

04

Model tenancy and roles

Map organizations, dealer accounts, markets, products, price lists and capabilities with explicit authority.

05

Design provisioning

Choose JIT, SCIM, invitation or administration; specify create, update, suspend, delete, reactivate and reconcile behavior.

06

Protect sessions and APIs

Set session, reauthentication, token, service identity, secret, environment and object-authorization controls.

07

Test failure and recovery

Cover invalid assertions, stale keys, removed groups, deactivation, IdP outage, duplicate users and locked administrators.

08

Operate the trust relationship

Monitor signing-key rollover, certificate expiry, mapping drift, inactive access, audit and incident ownership.

Federation and access security

Validate the assertion, then authorize the object.

  • Validate issuer, audience, signature, key, time, nonce, state and the exact protocol transaction according to the chosen profile.
  • Prefer stable provider-scoped subject identity; treat email, name and group claims as mutable attributes unless policy says otherwise.
  • Minimize requested claims and document why Configurix receives, stores, refreshes and deletes every identity attribute.
  • Enforce tenant and object authorization after authentication on every project, price, quote, order, document and administration request.
  • Prevent role escalation through untrusted claims, editable profile fields, ambiguous group names or unsupported identity providers.
  • Separate browser sessions, API access tokens, SCIM credentials, integration identities and emergency administrator access.
  • Protect signing keys, client credentials, certificates and SCIM tokens with rotation, environment isolation and accountable ownership.
  • Monitor sign-in anomalies, mapping failures, privileged changes, deprovisioning lag and repeated access to unauthorized objects.

Acceptance evidence

Test forbidden paths as carefully as successful sign-in.

  1. 1A valid user from the trusted IdP signs in once and resolves to exactly one intended Configurix account and tenant membership.
  2. 2An assertion with the wrong issuer, audience, signature, time, state, nonce or transaction context is rejected safely.
  3. 3Two identity providers issuing the same email address do not merge users unless an explicit controlled account-linking process approves it.
  4. 4Dealer A cannot read, guess, search, export or mutate Dealer B projects, customers, prices, quotes, orders or documents.
  5. 5Removing a user from the authoritative group or SCIM directory removes the intended role or access within the accepted time window.
  6. 6Suspension, deletion and reactivation preserve the correct audit history and do not accidentally restore obsolete privileges.
  7. 7Role and attribute changes affect only the permitted tenant, market, product, price and administration capabilities.
  8. 8Expired, revoked, replayed or logged-out sessions and tokens cannot continue protected actions beyond the documented policy.
  9. 9A sensitive action requires the expected recent or stronger authentication context and fails honestly when evidence is insufficient.
  10. 10Signing-key rollover or certificate renewal succeeds without accepting an untrusted key or causing an uncontrolled lockout.
  11. 11A service identity cannot use interactive customer or administrator flows and can access only its approved API objects and actions.
  12. 12Reconciliation identifies extra, missing, inactive, duplicated and privilege-drifted accounts across the identity provider and Configurix.

Failure patterns

Where enterprise SSO creates a false sense of security.

SSO is treated as authorization

A valid login is allowed to access every tenant, project or admin action because object policy was never designed.

Email is the permanent user key

A changed, recycled or identical cross-provider email links the wrong identity or duplicates a user.

Every IdP group becomes a role

Uncontrolled group naming or claims can grant pricing, publication or administration privileges.

JIT provisioning has no offboarding

Users are created at first login but never suspended when they leave the organization or dealer.

SCIM success means access is gone

The account changes, but existing sessions, tokens, tenant memberships or project shares remain active.

Logout promises too much

The interface says signed out while another Configurix session, IdP session or refresh path remains valid.

Service integrations impersonate people

ERP or CRM automation inherits human access and produces weak ownership, rotation and audit evidence.

The emergency account becomes normal

A break-glass identity bypasses SSO permanently and is shared, unmonitored or overprivileged.