Workspaces

How work is organised into organisations and workspaces, how to create and switch between them, and what happens when one is deleted.

A workspace holds one data product: its pipelines, datasets, dashboards, alert rules, integrations and chats. An organisation holds people, billing and any number of workspaces. Most teams keep one workspace per goal, for example “Competitor pricing UK” and “Store locator coverage” as two workspaces in the same organisation.

Organisations and workspacesAn organisation owns people and billing. It contains workspaces, each with its own pipelines, datasets, analytics and integrations. Members join at organisation level and can see every workspace in it.Workspace: Market Radarone goal, one set of dataWorkspace: Menu trackerprices, menus, venuesWorkspace: …Organisationpeople + billing ownerPipelinesDatasetsAnalyticsIntegrationsMembersjoin at organisation level
People and billing belong to the organisation. Everything else belongs to a workspace.

Organisation versus workspace

  Organisation Workspace
Holds Members, invitations, billing history Pipelines, datasets, analytics, alerts, integrations, chats, files, Jason memory
Who can see it Its members Every member of the organisation
Created Automatically at first sign-in (unless you were invited to one), or from the switcher From setup, or New workspace on the list
Row allowance — Per workspace, resets monthly
Jason email address — One per workspace

Membership is organisation-wide: anyone you invite can open every workspace in the organisation. There are no per-workspace permissions. See Team.

What lives in a workspace

  • Pipelines and their versions, runs and statements of work.
  • Datasets and every published version of them.
  • Analytics: dashboards built from the datasets.
  • Alert rules and their history.
  • Integrations: Slack, email, Sheets, webhooks, MCP grants and CLI sign-ins.
  • Chats with Jason: the build conversation and every change you have asked for since.
  • Workspace files and Jason memory (Settings → Content).
  • Settings: name, goal, icon, the sidebar layout, link access, billing cap, Jason email allowlist.

A chat, a pipeline or a dataset never crosses workspaces on its own. If you open a link to something that lives in another workspace you can access, Jsonify offers Switch and continue.

The Workspaces list

Open it from the workspace switcher (Workspaces tab) or at /workspaces. The page is headed Workspaces and lists every workspace in the organisation you are currently in, most recently updated first.

The Workspaces list page showing several workspaces with icons, goals and last-updated times, and a New workspace row
The workspace list for one organisation.

Each row shows the icon, the name, the goal (when it differs from the name) and when it was last updated. Rest the pointer on a row for its actions menu:

Action What it does
Rename Edit the name in place. Enter saves, Escape cancels. A blank name is ignored.
Delete Asks Delete “name”? with the warning that its pipelines, datasets and dashboards go with it. Delete confirms.

The last row is New workspace.

Creating a workspace

  1. Choose New workspace from the list, or Create workspace in the switcher.
  2. Describe the goal on the setup page and follow the flow on Your first pipeline. Jason proposes sources, fields and a schedule, then builds.
  3. Or skip the build. Under Advanced, Skip, just make an empty workspace creates a workspace named “New Workspace” and takes you straight to its Home page. Rename it in Settings.

Every workspace starts on the free allowance of 100 rows a month. Raising the cap is per workspace; see Billing.

Switching workspaces

The workspace name sits in the centre of the breadcrumb bar on every page. Click it (tooltip Switch workspace) to open the Switch dialog. On a phone, the same dialog opens from the workspace row in the menu drawer.

The dialog has up to three tabs:

  • Recent. Workspaces you have opened recently, across organisations. Shown only once you have visited more than one. A row’s menu offers Remove from recent.
  • Workspaces. Every workspace in the current organisation, with Create workspace when the list is empty.
  • Organisations. Every organisation you belong to, the current one marked Current, each with a preview of its workspace names. Organisations with no workspaces are folded behind View n more organisations with no workspaces.

Selecting a workspace loads it and opens its Home page. The last workspace you used is remembered per device, so the next visit lands there.

Search (⌘K), the rows-left meter and the Jason panel all belong to the current workspace. Switching workspace switches all three.

Switching or creating an organisation

On the Organisations tab, click another organisation to move into it. The page reloads on that organisation’s Home. You must be a member; membership is granted by invitation from someone already in it (see Team).

At sign-in, accepting an invitation takes you straight into the organisation that invited you. If you belong to several organisations, the sign-in dialog may ask you to Choose your organisation, showing a couple of workspace names for each and marking the one you used last. See How sign-in works for invitees.

New organisation at the bottom of the tab reveals a name field (Enter creates, Escape cancels). You become its first member and are switched into it. A new organisation starts with no workspaces, so the next step is Create workspace.

The footer of the dialog shows who you are signed in as, your organisation, and Log out.

Name, goal and icon

Three things identify a workspace, all edited in Workspace settings:

Field Where Notes
Workspace name Settings header, or General → Workspace Renaming changes the address bar slug but not the workspace’s Jason email address.
Goal General → Workspace One or two sentences. Jason reads it in every chat and uses it to ground suggestions on Home.
Icon The icon button in the Settings header Pick from the icon library, generate one from a description, upload an image, or use a website’s favicon. The icon appears in the switcher, the browser tab and the breadcrumb bar.

Set the goal even if the name says it all. “Track UK grocery prices for our 120 own-brand equivalents, refreshed daily” gives Jason more to work with than “Grocery prices”.

Moving a workspace to another organisation

If you belong to more than one organisation, Settings → General → Danger Zone has Move to another organisation. Choose the destination and press Move workspace. The workspace, its pipelines, datasets and runs move together; past billing stays with the old organisation and future usage bills to the new one. Members of the old organisation lose access, and you are switched across with it.

Deleting a workspace

Deletion is immediate and permanent. There is no archive state and no recovery.

  1. Open Settings → General → Danger Zone, or the row menu on the Workspaces list.
  2. Type the workspace name exactly as shown (Settings) or confirm the inline dialog (list).
  3. Press Delete Workspace. You are taken to the workspace list.

A workspace that has ever had billing enabled cannot be deleted this way. The attempt fails with Contact support to settle billing before deleting this workspace; email support@jsonify.com to close the billing account first.

Deleting removes every pipeline, dataset version, dashboard, alert rule, integration, chat and file in the workspace. Its share link stops working. Export any dataset you want to keep first; see Query and export.

Rows left, per workspace

Each workspace has its own monthly row allowance, shown as N rows left at the bottom of the sidebar. The meter counts rows collected this calendar month (UTC) against the workspace’s cap plus any once-off grants. Click it for the Monthly usage dialog.

When a workspace reaches its cap a red banner reads This workspace is out of rows and its pipelines pause until the month resets or the cap is raised. Other workspaces in the organisation are unaffected. Details on Usage.

What’s next

Connect your data assistant

Build datasets and work with your data in Claude, ChatGPT, Copilot or another assistant.

Connect in Claude

  1. Open the Jsonify connector: Open on Claude.ai ↗
  2. Select Connect and sign in to Jsonify.
  3. In a chat, enable Jsonify under + → Connectors and describe the data you need.
Advanced

Team or Enterprise account? Your workspace owner enables Jsonify once for everyone from Admin settings → Connectors. Jsonify is a community connector in the directory — some admins allow those by default, some review them first.

No directory? Add it by hand: Settings → Connectors → + Add custom connector, name it Jsonify, paste the server URL below, then Connect.

Server URLhttps://factory.jsonify.com/mcp

Official Claude custom-connector guide ↗

Then say: “build me a dataset of competitor product prices and availability, refreshed daily”. Full instructions per client on /connect.