@picked/client 0.0.101-next.2 → 0.0.101-next.3

package/dist/docs/reference/dashboard/projects.mdx

@@ -1,44 +0,0 @@
----
-type: reference
-layout: docs
----
-
-import { Screenshot } from '../../../../components/Screenshot'
-
-# Projects
-
-A project is one site or one application that you want to measure with Picked. Each
-project has its own experiences, content, and options.
-
-<Screenshot
-  route="/{orgSlug}"
-  alt="The organization home page on the Picked dashboard, with the projects in an organization"
-/>
-
-## Workspaces
-
-Each project holds one or more [Workspaces](/reference/dashboard/workspaces). In a workspace you set the
-options for an experience and you see a preview of it before you make it live.
-
-## Project home
-
-When you open a project, you land on the project home page. It shows your SDK
-snippet and a list of the setup tasks that are still open.
-
-Copy the snippet and add it to your site. The snippet connects your site to the
-project and lets Picked serve experiences to it. See
-[SDK Installation](/reference/sdk) for the setup detail.
-
-## Project navigation
-
-The sidebar shows the sections of your project: **Feature flags**, **Fields**, **Flows**,
-**Pages**, and **Workspace settings**. **Flows** holds **Step Layouts**, and **Pages**
-holds **Page Layouts** and **Sections**.
-
-A step, an action, and a condition have no sidebar entry. You reach all three from the
-library in the flow builder, because each one belongs to a flow.
-
-## Related
-
-- [How to create a project](/how-to/create-a-project)
-- [How to install the SDK](/how-to/install-the-sdk)

package/dist/docs/reference/dashboard/reports.mdx

@@ -1,43 +0,0 @@
----
-type: reference
-layout: docs
----
-
-import { Screenshot } from '../../../../components/Screenshot'
-
-# Reports
-
-A report is an embedded Metabase dashboard or question, attached to a Picked project. Use
-a report to see how your visitors move through your experiences and your feature flags.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/reports"
-  alt="The reports list for a project on the Picked dashboard"
-/>
-
-## Report options
-
-| Option | Description |
-| --- | --- |
-| **Report name** | The name that the reports list shows. |
-| **Description** | An optional note about what the report shows. |
-| **Metabase report type** | `Dashboard` or `Question`. |
-| **Metabase report ID** | The numeric ID from the Metabase URL. |
-| **Display order** | Optional. It controls the position of the report in the list. |
-
-The create form has a link that opens the report, so you can check that the ID is
-correct before you save.
-
-## Permissions
-
-A member needs permission in the organization to create, edit, or delete a report. The
-dashboard hides those actions from a member without it.
-
-## Delete a report
-
-Open the report settings page and click **Delete report**. You cannot reverse a delete.
-
-## Related
-
-- [Analytics queries](/how-to/analytics) — query the same data with SQL.
-- [About PickedQL](/explanation/how-pickedql-works) — what the query layer expands.

package/dist/docs/reference/dashboard/steps.mdx

@@ -1,37 +0,0 @@
----
-type: reference
-layout: docs
----
-
-import { Screenshot } from '../../../../components/Screenshot'
-
-# Steps
-
-A step is one screen or card that a visitor sees during an experience. Each step
-holds one or more fields. A field collects data or shows content.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/steps"
-  alt="The steps list for a workspace on the Picked dashboard"
-/>
-
-## Set up a step
-
-**Name**: The name that the dashboard shows. Your visitors do not see it.
-
-**Key**: The identifier that your application uses for this step. Your
-visitors do not see it.
-
-**Layout Name**: The name of the component layout that renders this step. Examples
-are `card`, `modal`, and `fullscreen`.
-
-A step can also carry a **Step Layout**. A step layout is a reusable CMS schema, and
-it gives the step a Content Entry. See [Models](/reference/dashboard/content/models).
-
-## Related
-
-- [How to add a step, a field, an action, or a condition](/how-to/add-a-step-field-or-action)
-
-- [How to build a flow](/how-to/build-a-flow) — add a step and assign fields to it.
-- [How to reuse a step, a field, or an action](/how-to/reuse-a-step-field-or-action)
-- [Models](/reference/dashboard/content/models) — the step layout schema.

package/dist/docs/reference/dashboard/team-management.md

@@ -1,29 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Team management
-
-Control who can reach your organization and what each person can do. An organization
-is the top-level container for your projects and members.
-
-## Organizations
-
-An organization groups your projects, your members, and your settings. You can belong
-to more than one organization.
-
-To move between organizations, use the organization control at the top of the
-sidebar.
-
-## Roles and permissions
-
-Each member holds a role, and the role controls what the member can reach. A role
-decides whether a member can create a project, edit an experience, control other
-members, or read a report.
-
-Give each member the smallest role that the work of that member needs.
-
-## Related
-
-- [How to invite and remove members](/how-to/invite-and-remove-members)

package/dist/docs/reference/dashboard/workflow-runs.md

@@ -1,142 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Workflow runs
-
-A run is one execution of a published workflow. An event or an action starts it. Picked
-records each run, each node that the run reached, and each lead that the run created or
-changed.
-
-## Where runs show
-
-| Page | Address                             | Content                                                                                      |
-| ---- | ----------------------------------- | -------------------------------------------------------------------------------------------- |
-| Runs | `…/workflows/<workflow>/runs`       | The runs of one workflow, the last run first. Open it with the **Runs** tab of the workflow. |
-| Run  | `…/workflows/<workflow>/runs/<run>` | One run: its records, its tasks, its details and its labels.                                 |
-| Lead | `…/leads/<lead>`                    | The **Workflow runs** card. It lists the runs that created or changed the lead.              |
-
-A run starts only from a published version of the workspace. A change to a workflow that
-you did not publish does not start runs.
-
-## Run status
-
-| Status      | Meaning                                                                                         |
-| ----------- | ----------------------------------------------------------------------------------------------- |
-| `Running`   | The run started and did not stop yet. A **Wait** node can keep a run in this status for days.   |
-| `Completed` | Each node that the run reached did its work, or failed and the run continued on its error exit. |
-| `Failed`    | A node failed. The run stopped at that node. The run shows the reason.                          |
-
-A tool node that fails with an edge on its error exit shows `Failed` on its task. The run
-continues on that edge only when the tool itself fails:
-
-- An External API call fails. Refer to the [External APIs reference](/reference/dashboard/external-apis#errors).
-- Another tool refuses the request. For example, a label value is not a number for a
-  `number` label, or the lead does not exist. The tool also refuses a row with `increment`
-  on a label that is not a `number` label. It refuses some project labels and run labels
-  with a key in the format of a hash. Refer to the [Labels reference](/reference/dashboard/labels).
-
-When the tool refuses the request, the error record has the code `tool_failed` and a
-reason from the tool, for example `value_invalid_for_type`, `label_write_invalid` or
-`owner_not_found`.
-
-Other failures stop the run, with or without an edge on the error exit:
-
-- A required argument has no value.
-- An argument has a value that the tool does not accept:
-  - The value has the wrong type.
-  - The value is not one of the options.
-  - A number is not in the range that the tool accepts.
-  - A label namespace or key does not have the correct format.
-  - Two labels have the same namespace and key.
-  - A list of labels is empty.
-  - A label row has `value` and `increment`, or neither.
-  - A label row has `increment` and `onlyIfAbsent`, or `increment` and a type other than
-    `number`.
-  - An `expiresIn` is not a whole number from 1 to 31536000.
-- A template cannot be rendered.
-- The workflow does not have a scope that the tool needs.
-- The tool gives output that is not valid.
-- An error occurs in Picked.
-
-## Visit cap
-
-A run can go back to a node that it reached before, on a loop. Each time that the run gets
-to a node is a visit. The visit cap is the maximum number of visits to one node in a run.
-
-| Setting       | Value                                                              |
-| ------------- | ------------------------------------------------------------------ |
-| **Visit cap** | A number from 1 to 100. If you do not set it, the visit cap is 10. |
-
-Set the visit cap in the workflow settings. In the definition of the workflow, the field is
-`maxNodeVisits`.
-
-A node can get to the visit cap. If the run then gets to the node again, the run stops.
-The run shows `Failed`, with the code `loop_limit_reached` and the ID of the node. Refer to [How to retry a failed call with a loop](/how-to/retry-a-failed-call-with-a-loop).
-
-When you save a workflow, Picked refuses these loops:
-
-- A loop that does not have a sleep node on it.
-- A loop that does not have a condition node on it.
-- An edge from a node to the same node.
-- A loop with the **Action response** node on it.
-
-## Records
-
-The **Records** card lists each lead that the run created or changed. It shows each lead
-one time.
-
-| Label     | Meaning                                                                                            |
-| --------- | -------------------------------------------------------------------------------------------------- |
-| `Created` | A node of the run created the lead. This label replaces `Updated` for the same lead.               |
-| `Updated` | A node of the run changed the lead or its labels.                                                  |
-| `Deleted` | A node of the run deleted the lead. This label replaces `Created` and `Updated` for the same lead. |
-
-When a lead does not exist now, the card shows `Deleted lead` and the ID of the lead,
-with no link.
-
-## Tasks
-
-A task is one visit to a node. The **Tasks** card lists the tasks in the order that the
-run reached them. When the run visits a node more than one time, each visit is a task.
-A task of a later visit shows the number of the visit, such as `visit 2`.
-
-The card shows 50 tasks. **Show more tasks** adds the next 50.
-
-| Column     | Value                                                                                                                                                             |
-| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Name       | The tool of a tool node, or the kind of node: **Start**, **Condition** or **Wait**.                                                                               |
-| Node       | The ID of the node. It links to the node in the editor while the workflow has the node.                                                                           |
-| Status     | `Running`, `Succeeded` or `Failed`.                                                                                                                               |
-| Time       | The time from the start of the task to its end.                                                                                                                   |
-| Operations | The leads and the labels that the task created, changed or removed, the first operation first. A label shows its namespace and its key. It never shows its value. |
-
-A condition task does not show which branch it chose.
-
-## Labels
-
-The **Labels** card shows the labels of the run. A user with `ORGANIZATION_PROJECTS_UPDATE` can
-change, add and remove them. Refer to [Labels in the dashboard](/reference/dashboard/labels#labels-in-the-dashboard).
-
-## Leads and runs
-
-A lead lists a run when a node of that run created the lead, set one of its labels, or
-removed one of its labels. A change to the labels of a lead is a change to the lead.
-
-The **Workflow runs** card shows 20 runs. **Show older runs** adds the next 20.
-
-## Access
-
-| Surface                          | Scopes                                                                                                                                                                        |
-| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Runs, Run                        | `ORGANIZATION_WORKSPACE_READ` and `ORGANIZATION_PROJECTS_READ`                                                                                                                |
-| The labels of a run              | `ORGANIZATION_PROJECTS_READ` to read them, and `ORGANIZATION_PROJECTS_UPDATE` to change them                                                                                  |
-| The **Runs** tab of the workflow | `ORGANIZATION_WORKSPACE_READ` and `ORGANIZATION_PROJECTS_READ`. Without these scopes, the workflow does not show the **Runs** tab.                                            |
-| Workflow runs card               | `ORGANIZATION_LEADS_READ` for the lead, and `ORGANIZATION_WORKSPACE_READ` and `ORGANIZATION_PROJECTS_READ` for its runs. Without the last two scopes, the card does not show. |
-
-## Deleted workflows
-
-A run stays after you delete its workflow. The run page and the lead card show it as
-**Deleted workflow**. The **Runs** page of a deleted workflow does not exist, and the run
-page has no link to the editor.

package/dist/docs/reference/dashboard/workflow-templates.md

@@ -1,182 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Workflow templates
-
-A template is text with `{{ … }}` in it. Picked fills it with data from the run before the
-node uses it. A tool node can have a template in each of its fields. A condition node can
-have a template in a text value of its rule.
-
-## Data that a template reads
-
-| Root              | Data                                                                   | Example                          |
-| ----------------- | ---------------------------------------------------------------------- | -------------------------------- |
-| `trigger`         | The event or the action that started the run.                          | `trigger.action.responses.email` |
-| `nodes.<node-id>` | The output of the last visit to a tool node. Refer to [Loops](#loops). | `nodes.n2.leads[0].id`           |
-| `run`             | The run. Refer to [Variables](#variables).                             | `run.startedAt`                  |
-| `workflow`        | The workflow. Refer to [Variables](#variables).                        | `workflow.name`                  |
-| `current`         | The node that reads the data. Refer to [Variables](#variables).        | `current.visit`                  |
-
-A template writes an index as `[0]`, such as `leads[0].id`. The `var` operator of a rule
-reads the same paths, and writes an index as a segment, such as `leads.0.id`.
-
-In the editor, the **Insert reference** button of a field shows the data that the node can
-read. The **Previous steps** tab shows `trigger` and `nodes`. The **Variables** tab shows
-`run`, `workflow` and `current`.
-
-## Variables
-
-| Path                | Type          | Value                                                                                     |
-| ------------------- | ------------- | ----------------------------------------------------------------------------------------- |
-| `run.id`            | Text          | The ID of the run, such as `wkrun_…`. In a test run, the ID of the test run.              |
-| `run.startedAt`     | Text          | The time that Picked recorded the run. In a test run, the time that the test run started. |
-| `run.preview`       | True or false | True for a run of the draft from a preview of the workspace, and for a test run.          |
-| `workflow.id`       | Text          | The ID of the workflow.                                                                   |
-| `workflow.name`     | Text          | The name of the workflow.                                                                 |
-| `current.id`        | Text          | The ID of the node that reads the variable.                                               |
-| `current.startedAt` | Text          | The time that the node started. If the node starts again, the time of the last start.     |
-| `current.visit`     | Number        | The number of the visit to the node, from 1. On a loop, each visit adds 1.                |
-
-A time is ISO 8601 in UTC, such as `2026-10-12T21:30:00.000Z`. The `date` filter changes the
-format and the timezone.
-
-Picked sets `run.startedAt` and `run.preview` one time, when it records the run. All the
-nodes of the run read the same values.
-
-Picked gets the `current` values when the node starts, and records the result of the node:
-
-- When a run continues after a stop, Picked uses the recorded results of the nodes that ran.
-  It does not run these nodes again.
-- If a node stops before Picked records its result, Picked starts the node again. The node
-  gets a new `current.startedAt`.
-- Picked does not start a failed node again. The run continues on the error exit of the node,
-  or stops at the node. Refer to the
-  [Workflow runs reference](/reference/dashboard/workflow-runs#run-status).
-- When the `retry` argument of an **External API** node is on, the node can send its request
-  more than one time. Each request uses the values that the node got when it started.
-
-When you save a workflow, Picked refuses a path below `run`, `workflow` or `current` that is
-not in this table. It also refuses `run`, `workflow` or `current` without a path below it.
-The error shows the path.
-
-## Loops
-
-A run can visit a node more than one time, on a loop. The path `nodes.<node-id>` gives the output of
-the last visit to that node that has a result. This is a visit that succeeded, or a visit
-that failed with an error.
-
-A node can read a node that comes after it on the loop. On the first visit, that node did
-not run, so the path has no value. In a condition, the value is `null`. In the editor,
-**Insert reference** shows these nodes with `(from the previous pass)`.
-
-## Templates in a condition
-
-A text value in a rule can have a template. Picked fills the template before it checks the
-rule.
-
-| Value                                                    | Result                                            |
-| -------------------------------------------------------- | ------------------------------------------------- |
-| Only one `{{ … }}`, such as `"{{ nodes.n2.count }}"`     | The value with its type. A number stays a number. |
-| Text with a `{{ … }}` in it, such as `"id-{{ run.id }}"` | Text.                                             |
-| Only one `{{ … }}`, with no value                        | `null`.                                           |
-
-A value that is only one `{{ … }}` must give text, a number, `true`, `false` or `null`. If it
-gives a list or an object, the condition stops with the code `condition_failed`. Text with a
-`{{ … }}` in it always gives text, also when the `{{ … }}` gives a list.
-
-Picked fills all the templates of a rule before it checks the rule. This includes a template
-in a part of `if`, `and` or `or` that the rule does not use. A template that gives a list or
-an object stops the condition, also when the rule does not use that part.
-
-A template in the rule of `map`, `filter`, `reduce`, `all`, `some` or `none` reads the data of
-the run. Picked fills it one time, before it checks the rule. It does not read the item.
-
-In a rule, only `{{` starts a template. A text value with only `{% … %}` in it stays as you
-write it. In a field of a tool node, `{% … %}` also starts a template.
-
-These values cannot have a template. Picked refuses the workflow when you save it:
-
-- The path of `var`.
-- The pattern and the flags of `regexp_matches`.
-- The message of `throw`.
-
-When you save a workflow, Picked checks each path in a template of a rule. It checks them as
-it checks a template in a tool node.
-
-## The `sha256` filter
-
-The `sha256` filter changes a value to its SHA-256 hash. The hash has 64 characters. Each
-character is a digit or a lowercase letter from `a` to `f`. You can use the filter in a tool
-node and in a rule.
-
-| Value                          | Result                                                                    |
-| ------------------------------ | ------------------------------------------------------------------------- |
-| Text                           | The hash of the text in UTF-8. Picked does not remove spaces in the text. |
-| A number, `true` or `false`    | The hash of the value as text. The number `42` gives the hash of `"42"`.  |
-| No value, `null` or empty text | Empty text.                                                               |
-| A list or an object            | The template stops.                                                       |
-
-The filter does not take an argument. A template that gives an argument to the filter stops.
-
-When a template stops, its node stops:
-
-- A tool node stops with a message that ends in `a template could not be rendered`. The node
-  does not use its error exit.
-- A condition stops with the code `condition_failed`.
-
-Picked does not have the `hmac_sha256` filter. When you save a workflow, Picked refuses a
-template that uses it.
-
-### A hash as a label key
-
-The namespace and the key of a label row can have a template. A hash fits the format of a
-label key. A namespace or a key has 1 to 64 characters, and a hash has 64 characters. A key
-that has a hash cannot have other text. Put other text in the namespace, for example
-`cms-lock-email`.
-
-When you save a workflow, Picked does not check the format of a namespace or a key that has a
-template. Picked checks the result when the node runs. If the result is not a correct namespace
-or key, the node stops. The node does not use its error exit.
-
-An empty key is not correct. Put the `default` filter before `sha256` when the template can
-give no value:
-
-```
-{{ trigger.action.responses.email | default: run.id | sha256 }}
-```
-
-## Example: a rule for a time of day
-
-This rule is true on days 1 to 5 of the week, from 08:00 to 16:59, in the timezone
-`Australia/Sydney`:
-
-```json
-{
-  "and": [
-    { "<=": ["{{ current.startedAt | date: '%u', 'Australia/Sydney' | plus: 0 }}", 5] },
-    { ">=": ["{{ current.startedAt | date: '%H', 'Australia/Sydney' | plus: 0 }}", 8] },
-    { "<": ["{{ current.startedAt | date: '%H', 'Australia/Sydney' | plus: 0 }}", 17] }
-  ]
-}
-```
-
-- `%u` gives the ISO day of the week, from 1 to 7.
-- `%H` gives the hour, from `00` to `23`.
-- `plus: 0` changes the text to a number.
-
-The offset of `Australia/Sydney` from UTC changes two times each year. The `date` filter
-follows the offset that applies on the date of the time.
-
-| Node started at, in UTC | Time in `Australia/Sydney`    | Branch  |
-| ----------------------- | ----------------------------- | ------- |
-| `2026-10-12T21:30:00Z`  | Day 2, 08:30, offset `+11:00` | `true`  |
-| `2026-06-12T21:30:00Z`  | Day 6, 07:30, offset `+10:00` | `false` |
-
-## Related
-
-- [Workflow test runs](/reference/dashboard/workflow-test-runs) — run the draft of a
-  workflow one time, and see the values that each node read.
-- [How to call an external API from a workflow](/how-to/call-an-external-api-from-a-workflow)
-  — read the answer of a call in a later node.

package/dist/docs/reference/dashboard/workflow-test-runs.md

@@ -1,77 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Workflow test runs
-
-A test run runs the draft of a workflow one time, with the trigger input that you give.
-It shows what each node did. It saves nothing, so you can test a change before you
-publish it.
-
-## Where to start a test run
-
-| Page     | Address                       | Content                                                                         |
-| -------- | ----------------------------- | ------------------------------------------------------------------------------- |
-| Test run | `…/workflows/<workflow>/test` | The trigger form and the result. Open it with the **Test** tab of the workflow. |
-
-You must have the scope `ORGANIZATION_WORKSPACE_UPDATE` and each scope that the workflow
-uses. The page names each scope that you do not have.
-
-## Trigger input
-
-| Trigger | Input                           | Meaning                                                                                                                                            |
-| ------- | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Action  | One input for each action field | The answer to that field. Nodes read it as `trigger.action.responses.<key>`. If a field is empty and not required, the run sends no answer for it. |
-| Event   | **Entity ID**                   | The entity that the event is about. Nodes read it as `trigger.entityId`. An empty field uses the workspace.                                        |
-
-Each action field gets the input for its type:
-
-| Field                  | Input                                              |
-| ---------------------- | -------------------------------------------------- |
-| Text                   | A text box.                                        |
-| Number                 | A number box. The value must be a number.          |
-| True or false          | A checkbox.                                        |
-| Record                 | A box for JSON. The value must be valid JSON.      |
-| Field with options     | A list to choose one option.                       |
-| Field with many values | Checkboxes for options, or one value on each line. |
-
-A required field must have a value before the test run starts.
-
-## What runs
-
-| Node                                                                                         | In a test run                                                                                         |
-| -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| Tool that reads, such as **Search leads** or an **External API** `GET` or `HEAD`             | Runs.                                                                                                 |
-| Tool that writes, such as **Create lead**, **Set lead labels** or an **External API** `POST` | Does not run. The result shows the input that it would send.                                          |
-| **Set run labels** and **Remove run labels**                                                 | Do not run, because Picked does not keep a test run. The result shows the input that they would send. |
-| **Get run**                                                                                  | Runs, and gives the ID of the test run, which starts with `test_`, and no labels.                     |
-| Condition                                                                                    | Runs, and shows the branch that it took.                                                              |
-| Wait                                                                                         | Does not wait.                                                                                        |
-
-A later node that reads the output of a skipped node gets no value.
-
-A test run does not wait on a loop. It goes around the loop until a condition takes the
-exit, or until a node gets to the visit cap. Each visit shows as a node of the result, and
-a later visit shows its number, such as `visit 2`. Refer to the
-[workflow runs reference](/reference/dashboard/workflow-runs#visit-cap).
-
-## Result
-
-| Status      | Meaning                                          |
-| ----------- | ------------------------------------------------ |
-| `Succeeded` | The node did its work.                           |
-| `Skipped`   | The tool writes, so the test run did not run it. |
-| `Failed`    | The node failed, and shows the reason.           |
-
-When a node fails, the test run stops at that node and shows `Failed`. If an edge leaves
-the error exit of the node, the test run continues on that edge as a run does, and can
-show `Completed`. Refer to the [workflow runs reference](/reference/dashboard/workflow-runs#run-status).
-
-Each node shows its input and its output. A test run does not show in **Runs**, and it
-does not create or change leads or labels.
-
-## Run variables
-
-A test run gives its own values to `run.id`, `run.startedAt` and `run.preview`. Refer to
-[Workflow templates](/reference/dashboard/workflow-templates#variables).

package/dist/docs/reference/dashboard/workspace-versioning.mdx

@@ -1,30 +0,0 @@
----
-type: reference
-layout: docs
----
-
-import { Screenshot } from '../../../../components/Screenshot'
-
-# Workspace versioning
-
-When you publish, Picked makes an immutable snapshot of your workspace. A project
-always serves exactly one version, the *live* version. A roll-back moves the live
-pointer of the project to an earlier snapshot. It changes no data.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/publish-history"
-  alt="The Publish history page with published workspace versions and the Live and Restore actions"
-  hide={['[data-testid="version-row-relative-time"]']}
-/>
-
-## Publish history
-
-The **Publish history** page lists each published version of every workspace in the
-project, the newest first. The version that Picked serves now carries a **Live**
-badge.
-
-## Related
-
-- [About workspaces and versions](/explanation/workspaces-and-versions) — why a roll-back
-  changes no data.
-- [How to roll back a published version](/how-to/roll-back-a-published-version)

package/dist/docs/reference/dashboard/workspaces.mdx

@@ -1,76 +0,0 @@
----
-type: reference
-layout: docs
----
-
-import { Screenshot } from '../../../../components/Screenshot'
-
-# Workspaces
-
-A workspace is one version of the configuration of your project. Use a workspace to hold
-a change, to see a preview of it, and to publish it when it is ready.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces"
-  alt="The workspaces list inside a project on the Picked dashboard"
-  hide={['[data-testid="workspace-row-relative-time"]']}
-/>
-
-## How workspaces work
-
-Each project has a workspace that holds your experiences, feature flags, steps, fields,
-actions, and conditions. When you make a change in the dashboard, that change stays in
-the workspace until you publish it. A change to a flow, to a feature flag, or to a step
-all behave the same way.
-
-A workspace is in one of three states:
-
-- **Live** — the workspace that the SDK serves to your visitors. Each project has
-  exactly one live workspace.
-- **Draft** — a workspace that no visitor sees. You can edit a draft, see a preview
-  of it, and publish it to make it live.
-- **Archived** — a draft that you put to one side. An archived workspace is still
-  editable, but it does not appear in the default workspaces list.
-
-## Change previews
-
-The publish modal shows a side-by-side change preview. It compares the current
-workspace against the last published snapshot. Use it to see exactly what your
-visitors get after you publish.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/experiences?action=publish"
-  alt="The publish modal with a change preview of added experiences, steps, and conditions"
-  selector='[role="dialog"]'
-  wait='[role="dialog"]'
-  hide={['[data-testid="publish-diff-replaces-version"]']}
-  renderWidth={720}
-  renderHeight={579}
-/>
-
-The preview puts the changes into groups: experiences, feature flags, steps, fields,
-actions, and conditions. Each row shows whether the record was **added**, **removed**,
-or **modified**. For a modified record, expand the row to see which properties changed.
-
-Some changes break other records. An example is a field that you remove while other
-steps still point at it. The change preview shows a banner above the diff for these
-entries, so that you can look at them again before you publish.
-
-The first publish of a workspace has no earlier snapshot to compare against. The
-publish modal shows the contents of the workspace as the first publish, with no diff.
-
-## Unpublished changes
-
-The workspace records whether anything changed since the last publish. The toolbar then
-shows a warning badge. It counts a change to any of these:
-
-- An experience or a feature flag.
-- A step, a field, an action, or a condition.
-
-## Related
-
-- [About workspaces and versions](/explanation/workspaces-and-versions) — why a draft and
-  a version are separate.
-- [How to see a preview of a workspace](/how-to/preview-a-workspace)
-- [How to publish a workspace](/how-to/publish-a-workspace)
-- [How to archive or delete a workspace](/how-to/archive-or-delete-a-workspace)