The connector ran in the wrong workspace
Available on Solo, Pro and Team.
If a run used another company's Brand Box, your AI picked a different workspace than you meant. You can fix it in one sentence.
Available on Solo, Pro and Team.
How a workspace gets chosen
The connector decides in this order:
- The one you name in the request. "Run a battle card for Tuskor in the Tuskor workspace."
- Your default workspace, if you've set one.
- Your personal workspace.
Every reply names the workspace the run used, so you can check it after each run.
Fix it now
- Ask your AI to list your workspaces. It shows your personal workspace, each team workspace, your role, and the projects inside.
- Re-run, naming the workspace and the project. For example: "Run launch messaging in the Tuskor workspace, project Route Optimization."
- If you want it to stick, ask your AI to set that workspace as your default. See Set your default workspace.
Common causes
- You didn't name a workspace and had no default. The run went to your personal workspace.
- Your default is an old one. Set a new default.
- Two workspaces have similar names. Use the exact name from the list.
- The project belongs to a different workspace. Name both.
- Your admin hid the workspace from the connector. Team admins can hide workspaces. If it doesn't appear in your list, ask an admin. See Connector controls for admins.
The wrong run still counts
A run counts against your plan wherever it went, so re-running uses another. A Pro tool run in a team workspace draws on the team's pool.
Stop it happening
Set a default workspace you work in most, and name the workspace on any run for another client. Agencies should name the client's workspace every time.
Next - Choose the workspace and project from your AI - Set your default workspace