Choose the context your decisions need.

Return a risk level, confidence, and consistent reason set for backend decisions and operator review.

Boundary: Available to provisioned workspaces; your application remains the final decision-maker.

Trace an assessment to named evidence categories instead of defending a black-box label.

Boundary: Visible according to workspace role and the evidence available for that event.

Translate risk bands into allow, watch, challenge, or block paths appropriate to each journey.

Boundary: Action paths require explicit tenant configuration; enforcement is not inferred from detection alone.

Review population shifts, disputes, and proposed adjustments before changing a production policy.

Boundary: Administrative review and additional approval may be required before a change is applied.

Find a device, review visits, compare profiles, and carry its identifier into a server-side workflow.

Boundary: History follows workspace retention and access settings.

Review browser consistency, privacy-browser context, and signs of automated or modified execution.

Boundary: Signals vary by browser support and are evidence inputs, not identity proof on their own.

Add challenge-backed browser or mobile integrity evidence when a higher-confidence decision needs it.

Boundary: Eligibility depends on the client platform, tenant policy, and an explicitly enabled challenge path.

Attach supported iOS or Android integrity context to a server-side assessment.

Boundary: Requires a supported mobile integration and the platform attestation service configured for the app.

Identify headless execution, automation residue, known operators, and suspicious interaction patterns.

Boundary: Detections are returned as evidence and reasons; response policy remains configurable.

Bring IP, hosting, transport, and reputation context into an investigation or score.

Boundary: Coverage and metering depend on enabled data sources and the selected service package.

Escalate selected traffic with an additional check instead of applying blanket friction.

Boundary: Challenge providers and tenant policy must be configured before this path is eligible.

Apply an approved allow, challenge, limit, or block policy before protected traffic reaches an origin.

Boundary: Requires a compatible edge deployment, explicit arming, and a tenant-approved response policy.

Review related identifiers and move from a population view to the evidence for one relationship.

Boundary: Relationship visibility is tenant-scoped and follows operator permissions.

Group recurring evidence patterns to prioritize coordinated abuse investigations.

Boundary: Shared-intelligence participation, where offered, requires separate tenant eligibility and controls.

Review, suspend, unlink, or delegate a supported device relationship through governed workflows.

Boundary: Available only for enabled relationship models and appropriately privileged operators.

Route contested decisions and account-recovery evidence into a reviewable case.

Boundary: Workflow availability depends on the identity product and roles enabled for the workspace.

Review a recorded journey, timeline, interaction evidence, and diagnostics from a dedicated session view.

Boundary: Recording begins only after tenant, domain, sampling, consent, and policy admission gates pass.

Inspect sampled web vitals, client errors, console diagnostics, and collection health by domain.

Boundary: Capture and read access are separately configured; sampling can remain at zero.

See navigation paths, interaction concentration, step completion, and drop-off across collected sessions.

Boundary: Results depend on enabled tracker collection, retention, and the selected tenant or domain scope.

Join an eligible in-progress session for consented support and investigation workflows.

Boundary: Payload access requires a separately authorized role and a session that is eligible for live viewing.

Track risk, usage, quality, and selected populations without rebuilding the same view.

Boundary: Available metrics follow the workspace package, data sources, and operator role.

Route selected events to an operational destination with tenant-scoped alert rules.

Boundary: A destination and alert policy must be configured; supported sinks vary by integration.

Create governed data exports and review the delivery history for periodic usage or status reports.

Boundary: Export scope, report delivery, and sensitive fields follow role and workspace policy.

Separate generated test traffic from customer events and review public component status and maintenance notices.

Boundary: Synthetic generation is an authorized test tool; status views report observed components without creating an availability promise.

Validate supported signed-agent requests and attach the verification result to the wider risk context.

Boundary: Requires compatible signing and edge integration; an unverified request is not automatically blocked.

Review agent identity, request evidence, and the resulting policy decision in one operator view.

Boundary: Agent verification and enforcement are separately enabled for eligible tenants.

Carry verified agent context into a supported server workflow without treating it as a human identity.

Boundary: Available only where the agent identity issuer, keys, and verifier have been provisioned.

Use an attested traffic decision to allow, limit, deny, or route eligible crawler access to a commercial flow.

Boundary: Commercial routing requires an approved payment integration and explicit tenant activation; it is not enabled by default.

Summarize and navigate the security, usage, and operational evidence the signed-in operator can already access.

Boundary: Requires assistant access, configured model capacity, and the operator’s existing permissions.

Let an approved external agent query scoped risk and operational data through read-only tools.

Boundary: Requires a scoped token and compatible MCP client; public tools do not authorize mutations.

Select approved providers, manage credentials, and review AI credit or model usage.

Boundary: Provider eligibility, model access, and usage limits depend on workspace configuration.

Review assistant activity, generated briefs, and any separately approved operator action trail.

Boundary: Oversight views are restricted by role; write actions, where present, require their own approval path.

Initialize collection through a browser API, framework wrapper, or configured script tag.

Boundary: Collection behavior follows the tenant, domain, consent, and feature configuration supplied at setup.

Verify results, look up supported resources, and make typed server-side calls with scoped credentials.

Boundary: Endpoints and scopes depend on the provisioned package and key permissions.

Connect supported iOS and Android attestation or capture flows to a backend assessment.

Boundary: Platform setup, app registration, and supported SDK capability vary by mobile integration.

Manage protected domains and connect eligible first-party relay, webhook, or event destinations.

Boundary: Each destination requires ownership, credentials, and tenant-specific configuration.

Run technical checks and site crawls, follow issue trends, and connect read-only Search Console data for an owned property.

Boundary: Checks require verified domain ownership; Search Console features require an approved Google connection.

Submit supported identity evidence, review verification cases, and route exceptions for operator review.

Boundary: Evidence types, screening, and provider-backed checks require an eligible identity configuration.

Collect supported evidence through browser or mobile capture flows and upload it to an authorized case.

Boundary: Device support, user permission, provider setup, and case policy determine eligible capture methods.

Bind supported credentials and require a stronger check for sensitive identity or operator actions.

Boundary: Requires compatible authenticators and an enabled credential or step-up policy.

Control who can enter the workspace and which data or actions each role can reach.

Boundary: SSO and advanced role controls depend on workspace configuration and an external identity provider where used.

Coordinate consent, browser privacy signals, sampling, legal basis, and feature policy before optional collection starts.

Boundary: The customer remains responsible for configuring an appropriate legal and consent basis for its use case.

Manage data lifecycle operations and preserve an auditable record of governed exports or deletion requests.

Boundary: Available operations and retention windows depend on data type, package, and operator authority.

Review operator activity, assistant actions, key posture, and access assignments from governed views.

Boundary: Sensitive audit and key details are role-restricted and tenant-scoped.

Keep workspace data scoped and review configured storage or processing locations where the deployment supports them.

Boundary: Location choices depend on the contracted deployment and do not imply a certification or universal residency guarantee.

Manage the people, protected properties, and workspace settings attached to a customer account.

Boundary: Administrative actions follow role, ownership, and workspace provisioning.

Review consumed capacity, package allowances, and separately provisioned modules or add-ons.

Boundary: Entitlements and limits come from the customer’s contracted package; code presence does not activate them.

Review account balances, order state, invoices, usage charges, and report delivery history where applicable.

Boundary: Payment methods, currencies, and billing views depend on the contracted commercial arrangement and operator role.

Reach customer support, request account deletion, and review public component or maintenance updates.

Boundary: Support channels and operational status are informational and do not add an unstated service-level commitment.