Set up your first VeriProof integration
Connect one development application and confirm its first recorded session. This verifies delivery. Testing whether policy prevents a protected action is a separate step.
Sign in to your portal
Use the customer portal URL assigned to your organization and its configured identity provider. Do not substitute a SaaS example URL for a customer-managed deployment.
Select a development application
Open Applications and choose the application you will connect. If you need a new application, create it when your role permits or ask an Administrator to provide access.
Use a readable name. Copy the assigned application ID for SDK configuration; the display name is not the ID. A selected SDK vocabulary supplies field names and values, not regulatory framework assignments.
Open Set up SDK
Select Set up SDK for the application. Confirm the environment before issuing or rotating a key. Store the complete key in your approved secret manager when it is shown.
Use the application’s current setup instructions for the ingest endpoint, application ID, and key configuration. Keep development credentials separate from production credentials.
Install the approved packages
Open Tools and SDKs, choose the language and framework packages, and run the displayed installation commands. Use the maintained example supplied with that package version.
If you prefer command-line setup, follow VeriProof CLI. Package access and an application’s runtime key have different purposes.
Send and inspect a test session
Run the setup example with synthetic data. Find its session under the selected application and environment. Open the record and compare the captured steps with the example you ran.
Check the input, output, and required fields that the example was intended to report. A successful local command without a matching session does not confirm delivery.
Never paste a real application key into source code, screenshots, or diagnostic notes. Load it from your approved secret store.
If the session is missing
Confirm the application ID, environment, key status, and endpoint.
Use veriproof doctor for sign-in and connectivity checks; it does not create a session.
Then follow SDK troubleshooting to investigate rejected or missing evidence. Do not label the test successful until the intended record is available.
Add the evidence your rules need
Open Required fields after the first session arrives. Review each field’s meaning and source before adding it. Send another session to check the update.
Developers maintain application fact shapes and source mappings. Governance Engineers review how those facts support policy. Use SDK quickstart for the field and ownership workflow.
When delivery is confirmed, follow Govern your first action. That scenario tests both an allowed action and a denied action whose side effect must not occur.