Onboard a new enterprise

  1. 01

    Open the Admin Console

    This task requires platform administrator access.

  2. 02

    Start the onboarding

    Enter the enterprise ID, enterprise name, and administrator email.

  3. 03

    Monitor provisioning

    Follow the live checklist until the enterprise reaches Pending SSO.

  4. 04

    Configure the redirect

    Copy the generated redirect URI into the authorised redirects for the enterprise's sign-in application.

  5. 05

    Confirm the login domain

    Record the email domain that should route users to this enterprise.

  6. 06

    Verify and activate

    Complete the check and confirm enterprise sign-in works.

Create a workspace

Use Workspaces → Create workspace in the enterprise Admin Console. Enter the name, review the derived immutable workspace ID, add an optional description, create it, and confirm it appears as Active. See the full tutorial.

Set up a workspace

Use MSOCK on the desktop with workspace admin access, open the workspace's Setup tab, answer whether it has existing SOCK knowledge, and let the one-time setup finish. See the full tutorial.

Upload legacy SOCK knowledge

When the workspace has existing knowledge, choose its docs/ folder, verify the replacement preview, supply a release label, publish, and confirm the distribution is active. See the full tutorial.

Manage feature availability

  1. 01

    Open enterprise or workspace settings

    Work at the scope that owns the constraint you intend to apply.

  2. 02

    Inspect the parent state

    Before changing a workspace, check the enterprise ceiling. A workspace can only narrow it.

  3. 03

    Apply the new state

    Enable or disable the capability, or leave it to inherit its registry default.

  4. 04

    Verify effective access

    Check role, surface, deployment, and inherited state — not only the local toggle.

Republish the organ pack

A workspace receives its /ws- lifecycle commands as a versioned organ pack. When a newer pack should be made available, republish it from the workspace's administration surface; members are then offered the update.

The pack a workspace receives follows its knowledge line: a workspace set up with existing SOCK knowledge stays on the legacy documents line, while a new workspace takes the MSOCK line.

Archive, restore, suspend, or rename

Open the target enterprise or workspace, choose the lifecycle operation, review the impact, and confirm the resulting state.

OperationUse it for
SuspendA deliberate, reversible access stop
ArchiveLifecycle closure
RestoreReversing an archive, where available
RenameA display-name change only — the workspace ID stays immutable

Triage a bug report

  1. 01

    Open Bug Reports

    Platform administrator access is required. The in-product Report a bug control is off by default and must be enabled per enterprise.

  2. 02

    Filter the queue

    Narrow by enterprise, severity, and status.

  3. 03

    Review evidence

    Inspect the submitted screenshot and diagnostic bundle under your privacy policy. A screenshot is limited to 5 MB and a diagnostic bundle to 50 MB.

  4. 04

    Update status

    Record the triage state and ownership.

Review devices

Platform administrators can see the fleet of machines running MSOCK, with the version each is on. See devices and bug reports.