Usage dashboards and alerts
Monitor worker usage, API calls, and resource consumption in real time.
Define what Vera may trust, use, and output before you scale
Use shared policies for research sources, confidence thresholds, channel activation, data exports, and cross-border movement—and enforce them consistently on every Vera task.
Entitlement management
Clearly see what is included in your plan and what requires add-ons.
Budget controls and limits
Set spending limits and receive alerts before unexpected overages.
Cost attribution by team and workflow
Identify which teams and workflows generate costs for better planning.
VERA POLICY WORKBENCH
Turn research boundaries into enforceable policy—not verbal guidance
Policies apply as Vera reads data, forms judgments, enables channels, and outputs results; violations are downgraded, routed for approval, or blocked.
Policy set: Global buyer research
Version 3.2 · Last updated 2026-07-30
Vera · All research tasksPublished
1Allowlist
Source policy
Define which public, authorized, and internal sources Vera may read and how evidence is weighted.
Current rule
Allow company sites, business registries, customer-licensed databases, and CRM; deny unknown data brokers.
Enforcement: Denied sources do not influence judgments, and source tier stays attached to evidence.
285% threshold
Confidence thresholds
Set verified, review, and unusable boundaries separately for companies, contacts, and channels.
Current rule
At least 85% passes automatically; 60–84% needs review; below 60% is downgraded.
Enforcement: Low-confidence results cannot be labeled verified or trigger automated outreach.
3Conditional
Channel policy
Control when Email, WhatsApp, phone, and other channels can be marked ready.
Current rule
Email requires verification; WhatsApp and phone require regional eligibility and known consent.
Enforcement: Channels that fail conditions remain pending or blocked.
4Gated
Export policy
Restrict exportable fields, purposes, file formats, recipient roles, and evidence scope.
Current rule
Only authorized sales roles may export personal contact data; exports over 500 records require approval.
Enforcement: Sensitive fields are masked automatically and oversized requests enter approval.
5Regional control
Cross-border policy
Control cross-border movement using data-subject region, storage location, and destination system.
Current rule
Cross-region transfer requires an allowed region, lawful purpose, and approved processing path.
Enforcement: Writebacks, webhooks, and exports that fail regional rules are blocked.
✓
2,418
Automatically allowed this month
✓
126
Routed to human review
✓
37
Blocked by policy
One policy set governs Vera’s source access, fact judgments, channel use, result exports, and cross-border delivery.