DevJock.aiOrganizations and Workspaces
How to create workspaces, add members, and manage access, which is scoped per workspace.
An organization contains one or more workspaces. A workspace is the tenancy and access boundary: tasks, memories, files, agents, prompts, chats, and integrations all live inside a workspace, and membership is granted per workspace. For the conceptual role a workspace plays in the brain, see the workspace page under The Brain.
Creating a Workspace
Workspaces are created from the workspace switcher in the app. Give the workspace a name and it becomes an isolated container for its own task tree, memories, and agentic assets. An organization can hold several workspaces, so you can separate work by client, team, or product line without mixing data across them.
You can also create and manage workspaces through the API. Each API has its own live interactive reference reachable from the app's user menu.
Adding Members
Add members to a workspace from its members or settings area. A person you invite gets access to that workspace only. Adding someone to one workspace does not grant them access to the others in the organization, so you add each member to each workspace they need to work in.
Access Is Per Workspace
Because the workspace is the access boundary, it is also the unit you plan around when structuring an organization:
- Keep unrelated efforts in separate workspaces so members and agents only see what they need.
- Put teams that share a task tree, memories, and agents in the same workspace.
- Remove a member from a workspace to revoke their access to everything inside it.