Skip to main content
Workspaces are where you collaborate in Script.it. Each workspace holds its own scripts and gives people and organizations a shared place to use integrations that have been shared with the workspace. When you sign up, Script.it creates a private workspace in your Personal account automatically. You can create additional workspaces for teams, clients, departments, or any other collaboration boundary.

​
Signing up

To create an account, go to app.script.it/login. You can sign in with Google or with an email address and password. No credit card is required to get started — your account comes with free included credits right away.
New accounts are on the free plan by default. You can upgrade to a paid plan at any time from Settings → Billing. See Billing, credits, and plans for details.

​
What workspaces contain

Each workspace contains:
  • Scripts - reusable workflows with blocks, source files, assets, and trigger configuration.
  • Members - the people and organizations that can view, run, or edit scripts in the workspace.
  • Shared integrations - connected accounts or custom integration types that members can use.
  • Triggers - rules that run scripts automatically on a schedule or in response to events.
Scripts are shared across sessions. If a member edits a script in one session, the updated script is visible everywhere that workspace is available. Session files are separate. Files produced during a run belong to the session that produced them, not to the workspace’s script source. See Session files for details.

​
Roles

Workspaces have two roles:
Workspace role does not automatically grant the right to manage an integration. Sharing, editing, rotating credentials, and deleting integration resources are controlled by per-integration permissions. A workspace Editor can still remove a shared integration from that workspace’s catalog for cleanup.

​
Sharing with people and organizations

New workspaces are private to their creator. Creating a workspace while an organization is active does not share it automatically. From the workspace’s Members dialog, an Editor can invite a person directly. An organization owner or admin who is also a workspace Editor can grant the entire organization Editor or Reader access. All current and future organization members inherit that role. Direct and organization access coexist. If you have both, Script.it applies the stronger role. A shared workspace appears in exactly one of each person’s accounts. Members of the owning organization reach it through that organization’s account. A person invited from outside the organization sees it in their own Personal account under Shared with you — they collaborate on the same scripts, and their runs use their own credits, their own connections, and any connection shared into the workspace itself. See Working in a workspace shared from outside. Script.it keeps at least one Editor for every workspace. Removing an organization’s access never leaves the workspace without someone who can manage it. See Organizations and active accounts for account switching, roles, and organization invitations.

​
Shared integrations

Workspaces can receive two kinds of shared integrations:
  • Shared connections - a collaborator shares their connected account with the workspace. The people it authorizes call that integration using the sharer’s upstream account.
  • Shared custom integration types - a collaborator shares the definition for an integration, such as the base URL, auth mode, OAuth client, or OpenAPI spec. Each authorized person connects their own credentials through that type.
Sharing a connection authorizes the account, not just a specific script or location — the people it reaches can use it from any of their sessions and scripts, and the same connection can be shared with multiple workspaces. A share reaches everyone the workspace grants access to, however that access arrived: Who owns the workspace does not narrow this. Instead, the decision is made when access is granted: only an organization owner or admin can add or remove an entire organization, and the sharing screen shows that connections shared into the workspace come along.
When you share an OAuth or API-key connection, the people the workspace authorizes can make requests under your authorization at the upstream provider. Those requests may appear as you in the provider’s logs or audit trail.

​
Accessing settings

To manage workspaces, open Settings → Sharing → Workspaces. From there you can:
  • Create a workspace
  • Rename or delete a workspace
  • Invite people or add an organization
  • Change a member’s role
  • Remove members
  • Review what integrations are shared with a workspace
To manage account-level settings, open Settings. From there you can:
  • View and edit your profile information
  • Check your credit balance and usage history
  • Upgrade your plan or manage billing
  • Review connected integrations and revoke access if needed
The pages in this section cover billing and security in detail.