Skip to content
Context docs

Organizations and workspaces

An organization is your company’s account in Context. Everyone at your company belongs to it, and admins manage it.

A workspace is a shared space for one client, team or project, such as “Northwind Capital” or “Q3 Launch”. It holds its own chats, files, skills and agents, and only its members can see them. You can belong to several. Every task runs inside a workspace, and its agents only use what that workspace can reach.

Switch workspaces, set one up for a client, write its default agent instructions, invite a teammate, pick a role and build a custom one (1:46).

Organization home

Click Home at the top of the left rail. Your workspaces are listed next to it, with a search box at the top. If no workspace is open, Home shows your organization’s home page, which has six places:

  • Drive: Your files.
  • Applets: Team apps.
  • Skills: How we work.
  • Automations: On a schedule.
  • Connectors: Connected apps.
  • Evals: Measure agents. It only appears if you have access.

You can’t start a task from the organization home. If you click Make or Build there, it asks which workspace to use.

Open a workspace

Click a workspace in the list. Its home shows a breadcrumb (“Organization > Workspace”), a greeting, the composer where you describe tasks, its projects, and “Pick up where you left off”. To get back to the organization home, click the organization’s name in the breadcrumb.

Click the workspace name at the top of the sidebar to switch. The menu lists every workspace you belong to, plus New workspace, Workspace preferences and Browse workspaces.

Right-click a workspace in the list and choose Pin to top, Hide from list or Workspace settings. Click the arrow next to it to see its tasks, channels, projects and drive.

Join or create a workspace

Choose Browse workspaces to see the open workspaces in your organization that you can join, and any invitations waiting for you. A Discoverable workspace has Join; an Invite only one has Request to join.

If you can’t see New workspace, your role doesn’t allow creating workspaces. An admin can create the workspace for you or change your role.

Set up a workspace

  1. Choose New workspace and give it a name people will recognize, such as the client’s name.
  2. On Access, choose who can get in:
    • Invite only: only the people you add.
    • Discoverable: anyone in your organization can find it and join.
  3. Create the workspace. It opens, and the sidebar shows its name.
  4. Open Workspace preferences and add a short Description and Default agent instructions. Every agent working here follows them, after your organization’s instructions and before the agent’s own. For example: “Cite the source file for every number.”
  5. Click Invite, search for a teammate and pick a role. Adding a person doesn’t add their agents: once they’re in, Context asks them Which agents do you want to bring in?

To see who is in a workspace, open Workspace settings > Members.

Roles in a workspace

RoleCan
ViewerLook at chats and shared items, but not change anything or send chats
MemberRead, edit and run things
AdminAlso manage members, files and settings
OwnerEverything, including delete the workspace

For a role in between, such as a client reviewer, open Workspace settings > Roles, click New role, and switch on only the permissions it needs.

Someone who joins a Discoverable workspace from Browse workspaces joins as a Viewer. An admin can raise their role in Members.

People outside a workspace can’t see its files unless they are shared with them or with the whole organization.

For admins

Admin setup: invite a new hire, group people, give the group a workspace and make it the default, read Roles, install a connector (1:25).
  • Staff a workspace once, not person by person. In Settings > User groups, make a group for the team, add the group to the workspace, and everyone in it gets the same role in one step.
  • Set a default workspace. In Settings > Workspaces, Default workspace is where new people land, whether they’re invited or sign in with single sign-on.
  • Seeing every workspace. Organization owners and admins can see every shared workspace, and can join one as owner from its settings.

Organizations on the newer permissions system: each workspace role is one step (see; see, create, edit and run; or also manage members and settings), and switching a permission moves the role to the step that matches. To enter a shared workspace, an admin takes admin of it instead of joining as owner. They must give a reason, and the reason is recorded.

Best practices

  • Create one workspace per client, team or project, not one per person. Everything in it is easy to share with its members, and nothing leaks to other teams; your own drafts belong in Your files.
  • Use Invite only for client work. Discoverable lets anyone in the organization join.
  • Write the default agent instructions when you create the workspace. A few lines on sources, tone and where to save outputs keep every agent in the workspace consistent.
  • Give the lowest role that does the job. Use Viewer for people who only read, Member for the people doing the work and Admin for one or two people who manage it, and a custom role rather than making someone an Admin.
  • Bring only the agents the work needs. An agent in a workspace can use what the workspace can reach.
  • Set up the workspace drive before the first task. A client folder with its sources uploaded means agents start from the right files. See Drive.
  • Pin the workspaces you use every day. In a large organization the workspace list gets long.
  • Review members when the work ends. People who no longer need access should be removed.

Next steps