Workspace vs Project Shared Steps

2 min read

Shared step scope controls where a reusable step group is available and who may be affected when it changes.

Workspace Shared Steps

Workspace shared steps are created from the workspace Shared Steps page. They are available to projects in the workspace and are best for flows that should stay consistent across projects.

Use workspace shared steps for:

Shared login flows
Common setup or cleanup flows
Organization-wide validation steps
Standard workflows used by multiple projects

Changing a workspace shared step can affect linked test cases across projects, so review usage before editing or deleting it.

Project Shared Steps

Project shared steps are created from a project Shared Steps page. They are available only inside that project.

Use project shared steps for:

Feature-specific flows
Project-only setup steps
Local validation patterns
Temporary or experimental flows

Project shared steps are safer for local changes because they affect only the selected project.

Scope on the Project Page

The project Shared Steps page can show both workspace and project shared steps. The Scope column identifies each shared step as Workspace or Project.

Use the Scope filter to focus the table on workspace shared steps, project shared steps, or both.

Locked Workspace Shared Steps in Projects

Workspace-level shared steps may appear locked when viewed from a project. This protects shared flows from being changed accidentally inside one project.

To update a workspace shared step, open the workspace Shared Steps page and edit it there.

Deletion Wording

Workspace shared steps use Delete because the action removes the shared step from the workspace.

Project shared steps use Remove where the action is available from the project page. The impact is limited to the selected project area and linked test cases in that area.

Choosing a Scope

Choose workspace scope when the flow is shared and stable. Choose project scope when the flow belongs to one project or may change independently.

If you are unsure, start with a project shared step. Move broadly useful flows to the workspace level once more projects need them.