Administration

What your admins configure, and what stays with Aurora Edge. Configuration that could produce an incoherent rating is validated before it can be saved.

Tenant setup

Aurora Edge

Users

Your admins

Forms and risk engines

Your admins

Intake labels

Your admins

API keys

Aurora Edge

Security settings

Your admins

Tenant setup

Aurora Edge provisions your tenant, sets its branding (name, logo, colour, default screening country), and runs data-governance actions on request. A tenant can also be suspended and reactivated as a reversible firm-wide freeze. Ask your Aurora Edge representative for any of these.

Users

Create staff accounts, set roles, move a user between tenants, disable or remove accounts. Role changes take effect immediately and invalidate stale sessions. The role model is in Roles and access.

Forms and risk engines

A visual form builder and risk-engine editor let you build and version intake pairs in the dashboard. Live coherence validation means an incoherent configuration cannot be saved.

Weights must sum correctly.
Every scored field must exist on the form.
Bands must be valid.

Editing is safe while cases are in flight

The form is frozen per application at creation and the risk engine at first evaluation, so revising an intake never changes what an in-progress applicant sees or what an approved rating was based on. See Core concepts.

Intake labels

Attach a label to a pair to make it live. Applications are provisioned against a label, not against a pair directly. The label id is what your systems send as the optional labelId when provisioning through the Onboarding API.

API keys

Aurora Edge issues, rotates, and revokes the keys your systems use, on request. The secret is shown once at issue and is not recoverable afterwards, so capture it into your secret manager at that moment.

Treat both rotation and revocation as taking effect immediately. Deploy the new secret to every caller before asking for a rotation, and expect requests still presenting the old secret to fail with 401 unauthorized rather than degrade gracefully. Because provisioning is idempotent, replaying a failed request with the new secret is safe and will not create a duplicate application.

Store the secret in a secret manager

Anyone holding an API secret can create applications and mint sign-in links for your tenant. Keep it server-side, never in source control. See Integration guide for the going-live checklist.

Security settings

Multi-factor authentication enrolment for staff accounts. Full detail is in Security and compliance.