Identify the deployed mode
Owner role · Operator
Evidence: API-token versus session-token behavior is confirmed for the endpoint.
Make the operation boundary visible
Scope planning matrixIllustrative case: an operator copies a working client setup but needs a different workspace for the current request.
| Boundary | Evidence needed | Decision if missing |
|---|---|---|
| Auth mode | Operator confirms the deployed contract | Do not infer mode from a copied example |
| Organization | Correct token claim or session header and membership | Clarify any mismatch |
| First read | Expected workspace evidence | Stop before expanding tool use |
Establish organization context
Owner role · Operator
Evidence: Token-bound organization or session header matches the intended membership.
Check the first read
Owner role · User
Evidence: A bounded read returns evidence from the expected workspace.
Decision to make: Verify the approved auth mode and organization binding before reading workspace tasks.
Filled illustrative decision
Invented planning text. Adapt it to your evidence and confirmed owners.
The fictional setup review finds that copied configuration still binds a different organization. The operator pauses task retrieval and establishes the intended auth context first. No real token or organization identifier is shown, and this planning decision does not prove the remote session is connected.
Questions about this workflow
Should both modes use the same organization header?
No. The source paths bind organization differently; follow the deployed mode.
Can I switch accounts to fix an access error?
Do not substitute another account or workspace without the user’s intended scope.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
Put the outline to work
- Ask the product operator for the deployed auth-mode contract.
- Use its organization-binding mechanism without borrowing another account.
- Stop on membership failure and clarify context rather than bypassing it.
From a useful outline to team work
Explore TeamBoostAI for your team
Verify the TeamBoost MCP server’s workspace context before reading or changing the records discussed in this guide. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.