Loading…
Self-Serve Workspace
Register once, issue credentials, and manage live policy safely
This workspace keeps zero-config onboarding intact: create the account, upload one representative sample, issue the org API key, connector, webhook secret, and current policy version, then come back here to add signal sources, version policy, update enterprise routes, and generate governance evidence or validation packs without handing the flow to Decionis ops.
workspace ID requiredonboarding grant not loadedorg key required for policy, routes, and governance
Workspace access
Use the sponsor onboarding grant right after account creation. After the first bundle is issued, the same org API key can reopen this workspace and manage policy, signal connectors, enterprise routes, and governance controls. Use the integration templates below when you need a product-specific destination instead of a generic webhook.
Zero-config next steps
- Create or version a signal-mapping session.
- Confirm the mapping baseline, then issue credentials.
- Use the same org key here to pause connectors, promote policy, configure routes, and keep governance evidence and validation packs current.
Credentials and current bundle
Select a confirmed mapping session to issue or rotate the org API key, connector ID, webhook secret, and policy version. This is the bundle enterprises drop into their deployment environment with no assistance.
No mapping sessions yet. Open the zero-config builder and upload the first signal sample.
Deployment env
Issue the first bundle to populate API key, connector, and webhook secret.
Signal sources
Mapping sessions are versioned so an enterprise can safely add a source, compare versions, and roll forward or back without overwriting the prior schema.
No signal versions yet. The first upload creates the source family, and each change can branch into a new version.
No live connectors yet. Issuing the first bundle creates the ingress endpoint for the selected source version.
Policy versions
Policy stays versioned. Workspace edits default to a new version, and only approval-managed policies stay editable in place. Setting a version current marks it active without destroying the version history underneath it.
Approval workflow
Approval-managed policies stay editable in place. Version-on-edit remains the default when approval gates are not defined.
No policy versions yet. The first saved policy becomes version one, and later edits create new versions by default.
Workflow routes and enterprise connectors
Configure template-backed routes for enterprise systems directly from the workspace. Presets turn integration templates into low-code starting points, while the raw JSON editors keep the route fully self-serve when a partner needs exact config.
No enterprise routes are connected yet. Save the first template-backed route to make orchestration self-serve.
Test output
Run a dry-run or live test to inspect route validation, request shape, and delivery output.