Apps and workspaces
A workspace holds work: its agents, teams, knowledge, records and rules. An app is a way of organizing that work. Workspaces install apps; one person can be in many workspaces.
The app rail
The rail at the far left of the dashboard shows:
- Workforce — always first; every workspace has it.
- Every other app the person has in any of their workspaces.
- Add app — opens Marketplace → Plugins (
/dashboard/marketplace/plugins).
Picking an app opens that app's nav. If the current workspace doesn't have the app, the nav opens with a workspace picker listing only the workspaces that do. Switching workspace keeps you on the same page when the target has the active app, and lands on Workforce otherwise.
The apps that ship
| App | What it is for | Made of | Opens at |
|---|---|---|---|
| Workforce | Agents and teams, what they know, how the workspace runs | Core (every workspace) | /dashboard/chat |
| Software Factory | Requests become approved work, verified changes and releases | Plugins software-factory, production-watch | /dashboard/p/products |
| GTM | Engagements, data rooms, proposals and growth work | Plugins proposals, data-rooms, growth-loop; surfaces personalization, discovery, proposals | /gtm/proposals |
Your assistant lives in your personal workspace, not on its own app tile. An Assistants app slot exists in the registry but is hidden until it ships.
How a workspace gets an app
An app ships no capability of its own. A workspace has an app when any of the app's plugins (or surfaces) is on there. Turn one on in any of three ways:
- Add app in the rail → Marketplace → Plugins, then switch the plugin on (workspace admins only). Vocion rewrites
workspace.yaml, keeping comments, and applies it. - In
workspace.yaml:
thenplugins: [software-factory]npm run workspace:apply -- <path> --project <slug>. Dependencies come with it (proposalsbringsdata-rooms). - From chat: an agent can recommend a plugin; accepting it runs the
plugin.enableaction.
The definitions live in vocion-core at packages/core/templates/apps/<id>/app.yaml and packages/core/templates/plugins/<slug>/.
Customizing an app is not a new app
To change what an app does in one workspace, override its plugin's files by slug in that workspace, or add a workspace page into one of the app's nav sections. See Customize an app.