Choose the workspace and project from your AI
Available on Solo, Pro and Team.
Tell your AI which workspace and project a run belongs to, and the right brand and context come with it.
Available on Solo, Pro and Team.
Say it in the request
Name the workspace and project the way you would to a colleague:
- "Run a battle card in the Northwind workspace, project Autumn launch."
- "Use the Tuskor workspace for this one."
- "Make this a private briefing." (team workspaces only, if your team allows it)
Names need to match exactly, ignoring capital letters. If two workspaces share a name, your AI is told to ask for the id instead. A project name works the same way inside the chosen workspace.
How the connector decides
For every call, it takes the first of these that applies:
- The workspace named in your request.
- The workspace tied to the API key you connected with, if any.
- Your default workspace. See Set your default workspace.
- Your personal workspace.
A name that cannot be resolved is an error, and the run does not fall back to something else. Your AI will say the workspace is not available. A workspace the team has hidden from the connector gives the same answer, so it cannot be told apart from a wrong name.
See your options first
Ask: "List my workspaces and their projects." This calls the list-workspaces tool (pmmagent_list_workspaces). It returns your personal workspace and every team workspace you can use, your role in each, which one is the default, and each workspace's projects.
Check the reply
Every run's reply names the workspace it ran in, and the project when you gave one, then whether the Brand Box was applied. On a team workspace it also says whether the briefing is visible to the team or private. Read that line before you trust the output. If it names the wrong place, say so and run it again with the right name. See The connector ran in the wrong workspace.