Organizations & Workspaces
Your organization is the top-level container for everything your business does on Rescale, and workspaces are the dedicated team environments inside it. You use workspaces to segment work by business unit, project, or region, apply different platform policies, and keep billing, hardware, and software portfolios isolated across teams. This page covers how organization administrators structure workspaces, how membership and admin delegation work, and which settings live in which admin portal.
Understanding the platform hierarchy
Every Rescale customer has a single organization. Inside the organization you have one or more workspaces, and every user belongs to at least one workspace. New organizations start with a Default Workspace, and every member lives there until you create additional workspaces.
Workspaces let you:
- Delegate administration to each team so they can manage their own members, projects, and resources.
- Apply different platform policies (hardware policies, software restrictions, core-count limits, storage caps) per team.
- Maintain isolated billing and invoicing per team while the organization stays the single contract holder.
- Pin compute and storage to a specific geographic region to reduce file transfer time and visualization latency.
Multiple workspaces are most useful for organizations with distinct business units, multinational teams, or large functional groups that operate mostly independently.
Creating additional workspaces beyond the default is available on ScaleX Enterprise. Contact your Solutions Architect or Account Executive to enable it.
Creating and managing workspaces
Only organization administrators can create, rename, or delete workspaces. From the Administration Portal, go to Teams > Workspaces.
To create a workspace:
- Click New Workspace.
- Enter a unique name (required) and an optional description.
- Save. Rescale assigns a workspace ID you will use for cross-workspace sharing and billing lookups.
To update a workspace, open it from the Workspaces page and edit the name or description. Names must be unique across the organization.
To delete a workspace, open it and click Delete Workspace. Deletion is permanent: the workspace, its users, and their data cannot be recovered. Drain or transfer data before you delete.
Region preferences are set by request. If you want a workspace to land in a specific region, contact your Account Executive or Solutions Architect.
Navigating between workspaces and admin portals
Hover your email at the bottom of the left sidebar. What you see there depends on the role you hold, which is deliberate: the menu shows only the portals you can actually open.
A colored banner across the top of each portal names the one you're in, worth glancing at, because the portals look alike and hold different settings.
To switch which workspace you're working in, use the workspace name at the top of the sidebar. The switcher lists each workspace with its ID.
The redesigned sidebar covers the user-facing platform. Both admin portals remain on the earlier top-nav layout. This is expected, not a stale page.
The two navs are not identical. The organization portal reads Dashboards · Activity · Policies · Teams · Financials · Security · Tools · Connectors · Integrations; the workspace portal has the same list without Connectors and Integrations, which are organization-only.
Each user has a default workspace, which is the one you land in at login, initially the first one your email was invited into. Change it yourself under Preferences > Default Workspace. See User Settings.
Seeing every workspace at once
Organization Admin > Dashboards > Overview is a structural inventory rather than a usage report. It renders one card per workspace in the organization, each showing:
- Projects, with how many groups are assigned to each
- Software and Hardware Policies configured for that workspace
- Groups, with each group's member count
- Workspace Admins, by name and email
- A View Portal link straight into that workspace's admin portal
Deactivated workspaces are labelled, and the organization's Default Workspace is marked.
This is the fastest way to answer governance questions that are otherwise tedious: which workspaces have no hardware policies, which have groups with zero members, which have accumulated more administrators than the work needs. It is also the quickest route into a specific workspace's portal when you administer several.
Because it is a summary of structure, it does not show spend. For that, see usage dashboards and billing summaries.
What lives in which portal
The two portals are not the same, and the split is deliberate: identity and contract-level settings are organization-wide; day-to-day operational policy is per workspace.
Three consequences worth knowing:
- Looking for retention, limits, or hardware policy? You're in the wrong portal if you're at org level. Those are all per workspace, in workspace settings and policies.
- Looking for SSO, password policy, or commitment plans? Those are org-only. A workspace admin can't reach them.
- Connectors and Integrations exist only at organization level. Object storage connectors, license proxies and hosts, VPN, and firewalls are configured once for the whole organization, so a workspace admin cannot set them up or change them.
Inviting members and delegating administration
Invite workspace users from Teams > Members inside a workspace administration portal. Users are invited by email, and a single organization member can belong to one or many workspaces.
There are two admin roles:
- Organization admin: full administrative access across the entire organization and every workspace.
- Workspace admin: administrative access to a specific workspace only.
Only organization admins can grant admin roles. From the organization's Teams > Members page you see every user with their workspace memberships. Use the checkboxes on each row to mark a user as an organization admin or a workspace admin for that workspace. Users in multiple workspaces can hold different admin roles in each.
Deactivating members and transferring their work
To remove a member, go to Workspace Admin > Teams > Members, open the member, and click Deactivate Member. A drawer confirms the action and gives you two options:
- Deactivate and delete files. All of the member's data is permanently deleted once their running workloads have shut down.
- Deactivate and transfer files. The member's workload files, meaning their jobs and workstations, pass to an Assigned Owner you nominate. Everything they uploaded outside a workload is deleted either way, so neither option preserves all of their data.
To find transferred work later, the assigned owner filters the Jobs or Workstations page by Assigned to me, or searches with the original owner's email using the syntax @username@domain.com. They can then work with it much as its original owner could. Transferring Performance Profiles or Workflows is not supported. See offboard a user for the full flow, what each option destroys, and why storage keeps billing against the departed member.
Sharing across workspaces
Sharing with a user in another workspace works like in-workspace sharing, with one addition: you specify the recipient's workspace ID along with their email. The recipient finds their own workspace ID in the workspace switcher at the top of the left sidebar, which lists every workspace they belong to alongside its ID.
By default only organization or workspace administrators can share jobs or storage devices across workspaces. To allow all members to do it, turn on the sharing setting in the organization portal.
Related
- Groups & Projects for the group and project constructs that budgets and policies attach to.
- Workspace Settings for the eight groups of per-workspace platform settings.
- Workspace Folders for how members organize jobs, workstations and workflows inside a workspace.
- Budgets & Deposits for workspace, project, and member-level spend controls.
- Billing & Reports for workspace and project billing summaries.