For the complete documentation index, see llms.txt. This page is also available as Markdown.

Workspace settings

Manage shared configuration with impact awareness.

Workspace settings influence people and resources across projects. Treat changes to ownership, permissions, storage, models, integrations, and subscription context as shared configuration changes.

Before you make the change

  • Identify affected projects, integrations, service identities, and owners.

  • Record the current state and reason for change.

  • Define a test and rollback or containment path.

Understand the product behavior

The workspace area includes:

  • workspace list and switcher;

  • general settings for name, purpose, and logo;

  • account security and 2FA;

  • billing and pricing portal;

  • usage and quota visibility;

  • members and member statistics;

  • Roles & Permissions editor;

  • API keys;

  • cloud storage connections;

  • user profile.

Usage can report datasource, image, video, medical, token, audio-duration, AI-inference, and member consumption. The interface warns when a downgraded plan would be exceeded.

Workspace destruction is intentionally different from leaving a workspace. It is Owner-only, requires the exact workspace name, and requires a second factor when the Owner has 2FA.

Members

Member management supports search, filtering, invitations, role changes, member actions, analytics, and Active, Pending, Disabled, and Rejected states. Pending invitations can be resent.

Change shared configuration safely

1

1. Open the correct workspace

Confirm workspace ID, owner, environment, and current settings.

2

2. Identify the control

Determine whether the change affects identity, storage, models, data, projects, releases, or subscription behavior.

3

3. Review dependencies

List the people, jobs, projects, and source systems that rely on the current setting.

4

4. Apply the smallest change

Use the minimum scope needed to achieve the intended result.

5

5. Test effective behavior

Verify expected access and resource operations with representative users or workloads.

6

6. Record and monitor

Capture owner, reason, affected scope, result, and next review trigger.

Decisions that affect production

Decision
Production guidance

Scope

Prefer project-level configuration when the requirement is not truly workspace-wide.

Ownership

Every shared integration or setting needs an accountable role.

Timing

Schedule high-impact changes around active tasks and automated workloads.

Recovery

Know how to restore service without reintroducing excessive access.

Continue the operating flow

  • Review membership and roles.

  • Re-test cloud and model integrations when shared settings change.

  • Update production-readiness evidence for material changes.


Explore related Unitlab capabilities: Unitlab’s data annotation platform