A CLI workspace selects one state instance for the same working directory and backend. A new workspace starts with separate state; it does not copy the infrastructure tracked by the previous workspace.
The same configuration can therefore propose new resources after you switch. Workspace names alone do not provide strong access control or a safe boundary between organizations. Independent configurations and backend permissions may be more appropriate for that separation. Practice creating a named workspace and applying its own service. Check the selected workspace before running any command that can change infrastructure, especially when the resource names look familiar.
A new CLI workspace begins with independent state.