Staff identity provider
Configure SAML sign-in, exchange metadata and manage staff account provisioning.
NIDAVARDFOUNDRY
GUARD EVERY GATEWAY
Enter the Foundry.
Checking sign-in configuration…
Sign in with Microsoft Entra →
Nidavard Security · Authorized staff access only
NIDAVARD SECURITY · GUARD EVERY GATEWAY.
Every client. One Foundry.
Manage client records, independent product licenses, and negotiated pricing.
Local development · Pricing records do not generate invoices or collect payments. Command remains bound to its configured tenant. The original development client's browser trial is synthetic.
FOUNDRY / PLATFORM SETTINGS
Platform settings
These settings apply to internal Foundry staff. Each client maintains separate Command identity and tool configuration.
Foundry administrator access
Grant access only to active, provisioned staff accounts. Customer roles cannot enter Foundry.
Client records, URL preferences, purchased capacity and commercial pricing are managed in Client administration. Browser policies are configured in the client's Command console.
CLIENT DIRECTORY
Add a client
Creates a separate client record. Licenses and prices start unconfigured.
SELECTED CLIENT
Client administration · Product licenses and prices are commercial controls. Configure browser behavior in the client’s Command console.
Adjust product entitlement
Capacity applies only to the selected product and client. Commercial status and technical validity are separate.
Identity count reconciliation
Client product pricing
Record the agreed rate per active canonical identity. Prices are independent for each product. No price is assumed; a zero rate must be explicitly saved.
Rates are internal commercial records, not invoices, quotes, tax calculations, or payment authorizations. Editing a price does not change licenses or technical access.
Client details
Client console address
The UUID address stays available. With client approval, reserve a shorter custom ID for the same workspace.
This records approval and reserves the name. DNS/tunnel routing, deployment host configuration and SAML Reply URLs need separate verification before the shorter URL is live. Existing UUID routing must be retained.
Client audit history
Staff actions and identity operations for this client. Changes include actor, reason, and before/after records.