メインコンテンツまでスキップ
This page is not translated yet. 日本語 is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Workspace Policies

section-index · Reviewed 2026-11-02 GA

Workspace policies decide what a member is offered when they set up a job: which coretypes, which software, how much can run at once, and how much can be downloaded.

A policy works by narrowing the choices rather than by checking the result. Instead of telling every engineer which coretype to pick and hoping they remember, you encode the rule once in the workspace admin portal and the platform applies it while they are choosing, so the option that would have broken the rule is simply not there. That also means a policy is invisible to the people it governs. They see a shorter list, not a refusal.

The four policies documented here​

The four differ in what they constrain. Two of them narrow the catalog a member picks from, one caps how much can run at the same time, and one caps how much data can leave. Only the first two are ones you compose yourself; the concurrency cap is set by Rescale and the download cap is a single set of numbers.

Hardware Policies
Control which coretypes appear for specific software and user groups.
Software Restrictions
Limit the workspace to an approved set of solvers. An empty list means no restriction.
Running Core Limits
View the concurrent core caps Rescale applies to your workspace, and how to raise them.
Download Restrictions
Cap files and data downloaded over a rolling period, with two alert thresholds.

The whole Policies menu​

The workspace admin portal's Policies section has eight entries. Four are documented above; the other four are covered elsewhere, because they belong with the feature they configure rather than with governance:

Policies entryDocumented at
Platform SettingsWorkspace Settings
Hardware PoliciesHardware Policies
Job Priority PoliciesJob priority
Software RestrictionsSoftware Restrictions
Custom FieldsCustom fields
Storage / Transfer LimitStorage & transfer limits
Running Core LimitsRunning Core Limits
Download RestrictionsDownload Restrictions

The organization portal's Policies section has only two entries: Platform Settings and Default Post Processing. Everything in the table above is per workspace, so if you are looking for one of these at organization level you are in the wrong portal.

Policies against platform settings

The two are easy to mix up because they live in the same menu. A policy controls which options appear during job setup, and it can be scoped to particular groups, which is what makes it useful for governing one team differently from another. Platform Settings sets workspace-wide defaults and limits instead, things like default walltime, retention periods, storage caps and template restrictions, and they apply to everyone in the workspace with no group targeting.

Both are workspace admin tools, so the practical question is whether you want a rule for some members or a rule for all of them. Note that Platform Settings is itself the first entry in the Policies menu, which is why people look for one in the other.