CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken in a support session, so the top of the screen shows a bar you will not see.
Where workspaces live
A workspace is the level between the team and its projects: the team owns the license, a workspace holds a set of projects, and projects hold captures. Team Settings › Workspaces lists every workspace in the team with its project count and creation date, and is where a new one is created.
Each row has an action menu with five entries: Open, Configure, Rename, Manage Access and Delete. Configure is the page this article is about; Manage Access opens the same Add Members dialog described below.
Creating a workspace
Create Workspace, top right of the list, opens a dialog with three fields: Workspace Name, an optional Description, and an Icon picker — a row of symbols that becomes the workspace's mark in lists and in the top bar's breadcrumb. Nothing else is asked at creation; members and projects are added afterwards.
Configuration › Properties
Inside a workspace, Configuration sits under Admin in the sidebar. Its first tab, Properties, is a single card: Workspace ID with a Copy control, Creator, Created Date and Workspace Name. The name is the only thing on it that can be changed here; it is the same rename the list's row menu offers.
The Workspace ID is what support will ask for. It is the stable handle for the workspace — renaming does not change it — and the Copy control exists so it is never retyped.
Configuration › Workspace Members
The second tab lists who has access to the workspace and at which of the two grades. Its Permission Levels card states the product's own one-line definition of each: Workspace Admin and Workspace Member. The grades themselves are explained in Workspace roles; this page is where they are handed out.
Giving someone access to a workspace is adding them as a member of it. There is no separate sharing surface in 5.0 — the Manage Access entry in the list's row menu and the Add Members button on this tab open the same dialog: pick people, choose Workspace Admin or Workspace Member, and optionally Notify people. The same shape repeats one level down, at the project, in Project configuration.
What a workspace cannot do
There is no workspace-level license, quota or default: those are the team's, on Team Settings › License and General, and a workspace inherits them. The License page's allocation table shows usage per workspace, which is the closest thing to a workspace quota — a reading, not a setting.
Deleting a workspace
Delete in the row menu asks once, and the dialog says exactly what will happen: “The workspace and the projects inside it move to Trash, where you can restore them.” Confirm and a Deleted toast follows; the workspace leaves the list. So deleting is not blocked by the projects inside, and it is not permanent: everything goes to Team Settings › Trash, which is where the permanent step lives (see Trash, restore and permanent deletion).