Workspace Overview
A workspace is a team’s private work area. In everyday life it is like a locked office: the people, files, and experiments inside it do not mix with the office next door. In CROForge it is the isolation boundary for experiments, Data Vista, events, website and app configurations, users, activity logs, and Smart Code. The Smart Code account-id is the workspace id, so the snippet on a customer site always reports into one workspace and never into another by accident.
Words used on this page
| Word | Everyday meaning | Meaning in CROForge |
|---|---|---|
| Workspace | A team’s private work area. | The tenant container that isolates experiments, Data Vista objects, events, websites and apps, users, activity logs, and Smart Code. Each workspace has its own id. |
| Isolation / isolation boundary | A wall that keeps one group’s work from mixing with another’s. | CROForge never mixes experiments across workspaces by accident. Each campaign runs under its own workspace id. |
| Workspace id | A unique number or code for that office. | The identifier in URLs such as /workspace/{workspaceId}/dashboard. The same value is used as Smart Code account-id. |
| Account ID / account-id | A customer number on an invoice. | In Smart Code URLs this is effectively the workspace id. Installing the snippet ties the live site to that workspace. |
| Smart Code | A small script you add to a website. | The client snippet (init.js) that assigns visitors, injects variation CSS/JS, and sends events. It is installed from Configurations → Websites and Apps, not from Settings. |
| Experiment | A controlled test to see what works better. | The API/model name for an A/B test (also called a campaign in the UI). Experiments live inside one workspace only. |
| A/B test / campaign | Comparing two versions to see which performs better. | The A/B area of the sidebar. Campaign is the UI name; experiment is the model name. |
| Data Vista | A place to look at and define data. | The area for attributes, segments, and metrics that you reuse across experiments in this workspace. |
| Attribute | A fact about a person or visit, such as device type. | A visitor or session property used in segment conditions (OS, browser, UTM, custom). |
| Segment | A named group of people who share something. | A reusable audience definition built from attribute conditions in Data Vista. |
| Metric | A number that tells you if you succeeded. | A reusable success definition (event plus conditions) stored in Data Vista and attached to experiments. |
| Event | Something that happened, such as a click. | A catalog entry (page view, click, custom) collected for this workspace. |
| Events catalog | The list of things you track. | The Events area of the sidebar for this workspace. |
| Website / app configuration | The record of a property you own, such as a site or mobile app. | Registered in Configurations → Websites and Apps. This is where Smart Code install belongs. |
| User | A person on the team. | Someone invited into this workspace with a role of Owner, Admin, or Member. |
| Activity log | A diary of who did what. | User activity and Workspace activity under Settings, scoped to this workspace. |
| Workspace selector | A switcher that changes which office you are in. | The control in the app chrome that changes your current workspace context. |
| App chrome | The frame around the page (header, sidebar), not the content itself. | Where the workspace selector and sidebar live in CROForge. |
| Dashboard | The home summary screen. | The workspace home at /workspace/{workspaceId}/dashboard. |
| Sidebar | The menu along the side of the app. | The map of Dashboard, A/B, Events, Data Vista, Configurations, and Settings for the current workspace. |
| Active | Turned on and in use. | A workspace status (WORKSPACE_STATUS). Active workspaces are the ones you should launch experiments from. |
| Inactive | Turned off or parked. | A workspace status. Inactive workspaces should not be used for new launches. |
Screenshot placeholder for this page: workspace-overview.png. Replace that file with a real screenshot and keep the same filename.
What a workspace isolates
Think of each workspace as a separate cupboard. You never mix experiments across workspaces by accident because each object is stored under that workspace’s id. A workspace isolates:
- Experiments (A/B tests / campaigns)
- Data Vista objects (attributes, segments, metrics)
- Events catalog
- Website and app configurations
- Users and activity logs
- Smart Code
account-id(the workspace id)
If two brands or a production site and a staging site must stay separate, use two workspaces. Metrics, events, and Smart Code will not leak between them.
Switching workspaces
Use the workspace selector in the app chrome to switch context. After you switch, the sidebar and every screen belong to the newly selected workspace. Routes look like this:
/workspace/{workspaceId}/dashboard
/workspace/{workspaceId}/ab-test
/workspace/{workspaceId}/data-vista/metrics
...The {workspaceId} piece is the same id Smart Code uses as account-id. That is why installing the snippet from one workspace never feeds data into another.
Sidebar map
Once you are inside a workspace, the sidebar is the map of that office:
| Item | Everyday meaning | What it is in CROForge |
|---|---|---|
| Dashboard | The front desk summary. | Workspace home summary. |
| A/B | The tests you are running. | List and manage experiments. See A/B testing overview. |
| Events | The list of things you track. | Event definitions for this workspace. See Events overview. |
| Data Vista | Building blocks for who and what you measure. | Attributes, segments, and metrics. See Data Vista overview. |
| Configurations | Which sites and apps belong here. | Websites and Apps, including Smart Code install. See Websites and Apps. |
| Settings | How this office is run. | General, Profile, Users, and activity. See Workspace settings. |
Workspace status
Workspaces can be Active or Inactive (WORKSPACE_STATUS). Active means the workspace is in use. Inactive means it is parked. Do not use inactive workspaces for new launches. Create or switch to an active workspace instead.
