Core Concepts

Script Studio Pro is built around a few core concepts that appear throughout the app and documentation.

Connected Service

A connected service is the management server Script Studio Pro authenticates to. The app stores the server URL as a saved service so admins can reconnect without retyping it.

When credentials are stored, they are stored in the macOS Keychain. Admins can clear saved credentials or remove saved services from Settings.

Script Library

The Script Library is the list of scripts loaded from the connected service. From the library, users can search scripts, select one for editing, refresh script metadata, select multiple scripts, export scripts, and delete scripts.

Script Editor

The editor is where the selected script is reviewed and changed. It provides line and character counts, current line and column, find support, helper snippets, copy, insert header, rename, category selection, save, export, duplicate, and revert actions.

Linked Policies

Linked policies are policies that reference the selected script. Script Studio Pro shows linked policy visibility so admins understand deployment impact before saving, deleting, unlinking, or preparing deployments.

Deployment Actions

Deployment actions help admins create a policy, link a script to an existing policy, unlink a script from a policy, or prepare a targeted deployment workflow.

Targeted deployment preparation uses a static computer group. The default group name is Script Studio Pro - Deploy, and admins can change it in Settings.

Script Runner

Script Runner is a separate test workspace. It can load a Script Studio Pro script, start a scratch script, run with runtime parameters, and display Output, Errors, Simulation, and Guidance.

Runner changes can be applied back to the selected script editor, but applying changes does not save them to the connected service. Review and save from the main workspace when ready.

Runtime Parameters

Runtime parameters simulate management server script parameters $4 through $11. These values help admins test scripts that depend on policy-supplied input.

Enterprise Simulation

Enterprise Simulation is a safer execution mode for testing management-style workflows. It can simulate policy context, management binary behaviour, protected path virtualization, API outcomes, packages, profiles, inventory updates, and common failure states.

Enterprise Simulation does not guarantee that a script will succeed in production. It gives admins stronger evidence before moving to a real test policy.