Application configuration

The Config tab holds the settings for one application. Each task has its own tab, so you can go straight to the setting you need. The tabs you see depend on your role and the application’s environment.

Developers see a shorter Config page that opens on the application key and starter code. Their field checks and test sessions are in Set up SDK.

A sandbox preview is read-only. It has no Keys or SDK fields tab, because there is no live key or traffic to manage.

Details

Application details describe what the application does, what a good outcome looks like, and which harms matter. The readiness checklist at the top shows what is still missing. Changing a description does not change a rule. To change how VeriProof responds to activity, use Governance defaults or Policy.

Execution channels and screen capture evidence

Declare how the application reaches its business systems. For browser and hybrid workflows, select the policy moments that require a masked browser-viewport capture. Set masking selectors and capture limits before the first test session.

The application declaration does not grant execution authority. Compare it with the observed channels in a representative session. See Govern computer-use applications.

Ownership

Every application needs a business owner and at least one developer. Owner gaps appear on the Administrator’s Home page until both are assigned.

Keys

Authorized roles can create, rotate, and revoke the application key and copy starter code. Administrators also see the key that lets the application confirm human review outcomes, and a history of key and access changes.

Store keys in your approved secret manager, never in source control or logs. For a planned rotation, check when the old key stops working and coordinate the application update. Verify the replacement in the intended environment.

If a key is exposed, revoke it promptly under your incident procedure. Do not wait for a routine rotation window or a successful replacement test. See Manage application credentials for the two workflows.

SDK fields

SDK fields shows which fields recent sessions included and which ones your policy checks, monitoring, and audit evidence still need. Start with a missing field that an active policy requires. See Instrumentation coverage.

Frameworks

Select the frameworks the application is assessed against. Selecting a framework starts an assessment. It is not a certification or a statement that the framework legally applies to you.

Governance defaults

These are the runtime defaults for this application: enforcement mode, policy controls, review routing, and the behavioral profile. Create and review reusable rules and alert thresholds in Policy. A request to change a production application opens here, beside the defaults it would change.

Evidence

Evidence brings together governance status, the contract template lifecycle, attestations, the third-party AI inventory, framework mapping, and live signal coverage. Open How these settings are applied to see the order settings take effect and where each current value comes from.

Lifecycle

Emergency stop, retirement, and deletion have different consequences. Check the named application and environment, then read what will stop or be removed before you confirm.

Check your work

1. Save the change on the tab you edited and check the confirmation.
2. Send a representative test session when SDK reporting changed.
3. Review Application Status, Policy, or Inbox for the expected result.
4. Use the history on Keys or Governance defaults to confirm who changed a setting and when.