Back to docsWho it's for

Join a team workspace

Accept a workspace invitation, find public agents and workflows, connect your own services, and complete a safe first team run.

Last updated August 28, 2026 · 5 min read

When you join a workspace, you gain access to the agents and workflows your team has made public. Your personal chats, connected accounts, and permission grants remain separate from other members.

Accept the invitation

You can join in either of these ways:

From the invitation email

  1. Open the workspace invitation.
  2. Sign in or create your account with the invited email address.
  3. Accept the invitation.
  4. When you see Invitation accepted, choose Switch workspace if the invited workspace is not already active.

From the workspace switcher

If you are already signed in, open the workspace switcher. Pending invitations appear with a Join action. Select Join to accept and activate that workspace.

If Okou says the invitation belongs to another account, select Switch account and sign in with the email address that received the invitation. Do not create a duplicate account to work around the mismatch.

Confirm the active workspace

The active workspace determines which public agents, workflows, members, and workspace settings you see. Before your first run:

  1. Open the workspace switcher.
  2. Select the team workspace named in the invitation.
  3. Open Agents and find the public agent your teammate named.
  4. Open Workflows and confirm the shared workflow is visible.

If the agent is visible but the workflow is not, ask the workflow owner to check that both the workflow and its owning agent are public.

Connect your own services

A shared workflow does not use another member's personal credentials. If the workflow needs Gmail, Notion, GitHub, HubSpot, or another service, connect your own account when prompted.

There are two separate steps:

  1. Connect the service. This identifies the account Okou can work with.
  2. Authorize the agent and grant requested permissions. This controls which named actions that agent can perform.

Review the account and scope before approving. If your team uses a shared service account, follow your organization's account policy; do not copy a teammate's token into a workflow instruction or chat.

Run the first shared workflow

Open the public agent that owns the workflow, then either:

  • enter its slash command, such as /qualify-inbound-lead; or
  • describe the task in natural language and provide the requested input.

For the first run, use a low-risk example and keep external actions reviewable. A good onboarding request looks like:

/qualify-inbound-lead

Input: [lead email or CRM link]
Create the qualification brief and a reply draft. Do not send the email.
Return the brief in this chat so I can review it first.

Check that the result:

  • follows the shared output format;
  • cites or identifies the required sources;
  • uses your intended connected account;
  • stops for approval where the instruction requires it;
  • goes to the correct shared destination only after review.

Give feedback that improves the library

Separate feedback about the shared method from feedback about one run:

  • Repeatable gap: “Every brief should show the source for employee count.” Ask the workflow owner to update the public workflow.
  • One-off correction: “This lead uses a subsidiary name.” Keep it in the current chat or source record.
  • Different team need: “Customer Success needs a different final format.” Consider a private copy or a workflow copy on another agent.

The goal is not to turn every comment into a new rule. Update the workflow when the lesson should apply to the next teammate and the next input.

Use it in Slack

If your workspace has installed the Slack integration:

  1. Connect your Okou account to Slack when prompted.
  2. Make sure Okou has been invited to the channel.
  3. Mention Okou and include the workflow name and task input.
  4. Continue follow-ups in the same Slack thread.

Use a direct message for private drafts or sensitive analysis. See Use shared workflows in Slack for setup and examples.

Troubleshooting

I joined but cannot find the workflow

Confirm you are in the correct workspace. Then ask the owner to verify that the workflow is Public and the owning agent is available to members.

The workflow asks me to connect or authorize a service

That is expected when the task needs access you have not granted. Connect your account, review the requested permission, and continue the run. Your teammate's authorization is not inherited.

I accepted with the wrong account

Use Switch account and sign in with the invited email. Ask an Admin to revoke and resend the invitation if the address itself was wrong.

My result differs from a teammate's

Check the input, active agent, connected account, source data, and workflow version. A shared procedure reduces variation, but different source records or permissions can still produce different results.

For the workspace setup side, see Invite teammates. To understand access boundaries, see Permissions.