メインコンテンツまでスキップ
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.
how-to · Reviewed 2026-11-02 GA

Workspace Settings

Workspace platform settings are where most of a workspace's behavior is set: defaults members inherit, limits they cannot exceed, and what they are allowed to create. They apply to one workspace, so two workspaces in the same organization can behave quite differently.

For the small set of policies that apply across every workspace at once, see Organization Settings.

Workspace Admin > Policies > Platform Settings is where most workspace behavior is set. Settings are grouped into General, Job, Template, File, Autosharing, Performance, Workstation, and Compliance. Each group saves independently, so you have to click its own Update button.

The ones with the widest effect:

SettingGroupWhy it matters
Require jobs to be assigned to a projectGeneralMakes project-level budgets enforceable. Set up groups and projects first, or this blocks job submission
Default hardware priorityGeneralSets On Demand Priority or On Demand Economy for every new job — see job priority
Allow non-admins to view core prices and billing summariesGeneralCost transparency, on or off. Turning it off also reduces a member's Charges/Usage page to usage only, and hides their Credits/Deposits page
Default job walltimeJobApplies when a user leaves Maximum Job Duration blank, which is what stops a job running indefinitely. Users can still override it
Template settingsTemplateCan restrict template creation — or all job creation — to admins only
File settingsFileThe two retention controls
Share with workspace administratorsAutosharingGives workspace admins visibility of members' work without being added to each project
Run Time MeasurementPerformanceWhether performance data counts execution time only or total run time
Allowed UsersPerformanceWho can see performance data: everyone, admins only, or named groups
Auto-terminate suspended workstationsWorkstationA days limit — see workstation limits
Requiring a project can block job submission

Turning on Require jobs to be assigned to a project means a member cannot submit a job until they belong to a group, that group is assigned to a project, and the project has a budget. Set the groups, projects, and budgets up first, or members will be blocked as soon as you save.

Workspace settings, grouped. Each group has its own Update button, so save the group you changed.
Template Settings is a governance lever

"Only allow admins to create custom jobs or desktops without using a template" means users can run only pre-approved configurations. That's the strongest control available over what hardware and software get used, and it's easy to miss.