Skip to main content

Workspaces vs. Assessments

One of the most common points of confusion for new organizations is determining when to create a new Workspace versus when to simply create a new Assessment. This guide clarifies the strategic intent of each to help you maintain a scalable hiring architecture.


Strategic Overview

Create a Workspace for Strategic Isolation

Workspaces are high-level organizational boundaries. They are designed for long-term separation of data, team access, and asset libraries. You should create a new workspace when you need to separate:

  • Geographic Regions: (e.g., Valens Datalabs US vs. Valens Datalabs Asia) Keep regional candidate data and local hiring team access completely separate to comply with data residency or regional hiring workflows.
  • Large Departments & Business Units: (e.g., Valens Datalabs US - Data Science vs. Valens Datalabs US - Sales) Ensure that technical challenge libraries and candidate profiles are only visible to the relevant departmental teams.
  • Subsidiary Companies: Manage different brand entities under one parent account while keeping their recruitment pipelines entirely distinct.

Create an Assessment for Tactical Hiring

Assessments exist within a Workspace. They are the individual evaluation units used for specific hiring needs. Create a new Assessment for:

  • Specific Job Openings: (e.g., Senior Python Developer - Q3 Hiring)
  • Recurring Programs: (e.g., Summer 2026 Engineering Internships)
  • Skill Benchmarking: One-off evaluations for existing team members or specific certification rounds.

Comparison Table

FeatureWorkspaceAssessment
DurationLong-term / PermanentTemporary / Campaign-based
Data ScopeContains multiple assessmentsContains individual candidates
IsolationHard boundary for Users and LibrariesShared within the workspace
Naming ExampleValens Datalabs Asia - App DevFrontend React Lead - Feb 2026

Why Isolation Matters

Using Workspaces correctly ensures that your Technical Challenge Library stays organized. Technical leads in the "Data Science" workspace won't have their library cluttered with "Sales" personality tests, and HR partners in "Asia" won't accidentally view "US" candidate reports.

tip

Always use a clear naming convention for Workspaces like [Region] - [Department] to make navigation intuitive for global administrators.