All posts
Product2026/11/04

ValidReach workspaces and teams: roles, budgets and shared results

How workspaces, member roles, team credit limits, result-sharing controls and scoped API keys work in ValidReach.

Agencies and multi-product companies often verify email lists for several clients or departments at once. ValidReach workspaces and teams separate access, spending limits and result visibility without requiring a separate login for every project.

Workspaces separate projects and access

Every account starts with a personal default workspace, and you can create additional shared workspaces from the dashboard switcher. Each workspace has its own members, teams, verification history, batch jobs and audit log under /settings/workspace.

Three workspace roles: owner, admin and member

  • Owner: full control over workspace settings, members, teams, credit budgets and ownership transfer (for non-default workspaces).
  • Admin: can invite or remove members, create teams, set team credit limits, toggle team result sharing and view the workspace audit log.
  • Member: can run verifications within assigned teams and view their own records plus records from teams where result sharing is enabled.

Teams, credit limits and result sharing

Inside a workspace, admins can group members into teams under /settings/teams:

  • Team credit limit: cap how many credits a team may spend so one campaign or client integration cannot exhaust the entire balance.
  • Share results toggle: when enabled on a team, members of that team can view verification history, batch jobs and CSV exports created by teammates; when disabled, members see only their own rows while owners and admins retain workspace-wide visibility.
  • Scoped API keys: under /settings/apikeys, keys can be scoped to a workspace and team so automated pipelines follow the same budget and visibility rules.

Sources

All posts