An HCP Terraform workspace groups the configuration and state for one collection of infrastructure. It also has its own variable settings and run history.
This is a broader boundary than a CLI workspace, which selects a different state for the same working directory. Split hosted workspaces where ownership or access needs a separate boundary. A development label alone doesn't restrict who can approve production changes. Check the selected workspace and its configured permissions before a run. These exercises use fictional team requests to test that distinction; the browser doesn't create hosted workspaces or authenticate with HCP Terraform.
The hosted workspace connects a configuration and its state to the team allowed to operate it.