メインコンテンツまでスキップ
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

Organization Settings

Organization settings are the policies that apply to every workspace at once. There are only three groups of them, and that is the point: the organization portal holds contract, identity, and cross-workspace concerns, while almost all day-to-day policy is set per workspace.

Find them at Organization Admin > Policies > Platform Settings. Only organization administrators can reach this page.

All three organization-wide policy groups. The left rail has two entries; the workspace portal's has eight.
Most settings are not here

The organization portal's Policies section has two entries. The workspace portal's has eight. If you are looking for hardware policies, software restrictions, file retention, core limits, or job walltime, you are in the wrong portal. See workspace settings.

Sharing Settings​

Allow workspace members to share objects across organization workspaces.

By default, only organization and workspace administrators can share jobs or storage devices with a user in a different workspace. Turning this on extends that ability to every member.

Cross-workspace sharing always needs the recipient's workspace ID as well as their email address, whoever is doing the sharing. Members find their own workspace ID in the workspace switcher. See sharing across workspaces.

Job Settings​

Allow non-admin members to view all pending and running jobs within the organization.

Turning this on lets any member see the organization-wide job list and the pending job queue, not just their own work. Administrators always see everything.

Custom Job Field.

Adds an organization-defined field to job submission. If you want per-workspace metadata instead, use custom fields in the workspace portal.

Compliance Settings​

Identify this platform with a header badge. Displays a badge in the platform header naming the environment. Useful when your users have access to more than one Rescale platform and you need them to be able to tell at a glance which one they are in.

Require agreement to terms when signing in. Presents text you supply, written in Markdown, that every user must accept before they can use the platform.

Declining signs the user out

A user who declines the agreement is signed out immediately, and the refusal is written to the audit log. Treat this as a gate on access, not a notice.

What is not on this page​

Some organization-wide controls live elsewhere in the organization portal rather than under Policies:

SettingWhere
Default post-processingPolicies > Default Post Processing
Single sign-onSecurity > Single Sign-On
Password policySecurity > Password Policy
Multi-factor authenticationSee MFA
Creating and deleting workspacesTeams > Workspaces
Granting administrator rolesTeams > Members
Commitment plansFinancials > Commitment Plans