Workspace and settings

Workspace and projects

A workspace is one product. It has an id, and everything in the Studio is scoped to it: journeys, runs, checks, monitors, recordings. Add a project when you have a second surface; each project has its own id for the Behavior SDK tag, so a marketing site and an app stay apart even on the same account. Switch between them from the workspace name at the top of the sidebar.

Keys and allowed origins

Setupshows the Behavior SDK tag with the workspace's id filled in. The tag can only send behaviour events; it can't read anything, and events are accepted only from the origins listed under Allowed origins. Add every domain you capture from, staging included if you want it.

Keys holds API tokens for the CLI and CI. Each token is named, shows when it was last used, and can be revoked on its own. Use one per machine or pipeline, so revoking one doesn’t take the others down.

Team

Invite teammates by email under Team on the Workspace page. Owners and admins manage keys, origins, credentials, integrations and the GitHub App; members see everything and can run simulations. Invitations count against your account’s invite codes while access is invite-only.

Privacy and masking

The Behavior SDK records behaviour only — no text, values or identity — so there is nothing to mask; see Capture. Capture can be turned off here for the whole workspace.

Credentials for simulations

If your product is behind a login, store a test account here: the sign-in page, the email and the password. Simulated people sign in with it once per run when Sign in first is ticked, and it is the default whenever a sign-in is stored. The password is encrypted at rest and never shown again; members can see that a sign-in exists, owners and admins can replace or remove it.

Use a dedicated test account, not a real user’s. The simulated people will do what the flow asks with it, including creating and changing things, and they are told never to delete anything.

GitHub

GitHub is where an owner or admin installs the GitHub App, once; the installation belongs to the workspace, not to whoever pressed the button. Connect a repository to the project and every pull request gets a check run named Simulathic and one comment edited in place, with no workflow file and no token in the repository, and the project’s journeys are written from the repository’s code. See GitHub App and Pull-request checks. Uninstalling the App on GitHub disconnects it: the checks stop and nothing else in the workspace changes.

Integrations and billing

Integrations connects Slack and email alerts; see Monitors and alerts. Billing, on the Workspace page, shows the plan, this month’s simulated sessions against what the plan includes, and the monthly cap you can set so a run or a monitor can never surprise you.