Workspaces
What a workspace holds, personal and shared workspaces, how workspaces differ from environments, and ways to organize them by team, by audience, or for an agent or Slack channel
A workspace is where people use published packages in the Credible app. It holds a set of packages, the chats about them, and the reports saved from those chats. The in-app agent answers from the packages in the workspace you ask in.
Personal and Shared Workspaces
- Personal workspace (shown as My Workspace). Everyone has one. It includes every package you can read, and its chats and reports are yours. Organization admins can read personal workspaces but cannot change them.
- Shared workspace. A named set of packages shared with people and groups. Every member can see its packages, chats and reports, and can start chats and save reports. Any member of the organization can create one.
Adding a package to a shared workspace gives everyone in the workspace read access to it. For that reason, adding a package takes two roles: manager of the workspace, and admin or modeler of the package's environment. Share with a Workspace covers creating one, its roles, and adding members and packages.
Workspaces vs. Environments
An environment is where data models are built and published. A workspace decides who uses them: it brings together the packages a team needs, with its chats and reports, and shares them with people and groups. One package can be in many workspaces, and one workspace can hold packages from several environments.
| Environment | Workspace | |
|---|---|---|
| Holds | Connections and packages | A set of packages, with chats and reports |
| Changes through | Modeling and publishing | Asking questions and saving reports |
| Who manages it | Organization and environment admins | Workspace managers; any member of the organization can create one |
Ways to Organize Workspaces
By team
Each team gets a shared workspace with the packages it works with. The team's chats and reports stay with the team, and a new member who joins the workspace finds them there.
By audience
A small, curated workspace for one audience, for example leadership, holds only the packages that audience needs. With fewer packages, the agent searches less and picks the right fields more often.
For an agent or channel
Each shared workspace has its own MCP URL, so a chat client or custom agent connected with it sees only that workspace's packages. In Slack, a channel is pointed at one workspace with /credible_set_workspace, and the bot answers from that workspace's packages.
How packages and connections are grouped into environments is covered in Environments and Packages.