Invite people after you have at least one public agent and one tested public workflow ready for them. This gives a new member an immediate starting point instead of an empty workspace.
Workspace invitations are managed from Settings → People.
Prepare the workspace
Before sending invitations:
- Make the agent teammates need Public.
- Publish the workflow they should use first.
- Remove credentials and sensitive one-off data from its instruction and files.
- Decide who needs the Admin role and who only needs Member access.
- If the team will work in Slack, have an Admin install the workspace integration.
- Write down the first task, required input, and expected destination for the onboarding run.
You do not need to connect every teammate's personal services in advance. Each member connects their own account after joining.
Send an invitation
- Open Settings.
- Select People. This page shows who has access to the workspace and any pending invitations.
- Select Add member.
- Enter the teammate's email address.
- Choose a role: Admin or Member.
- Select Send invitation.
The invitation remains pending until the recipient accepts it. You can return to Settings → People to review or revoke a pending invitation.
If Add member opens an upgrade prompt, the current plan does not include workspace invitations. Follow the in-product upgrade path before trying again.
Choose the right role
| Role | Use it for | Typical responsibilities |
|---|---|---|
| Admin | People who manage the workspace itself | Invite members, manage workspace settings and billing, install workspace-level integrations, and govern shared access |
| Member | People who use Okou in their daily work | Run public agents and workflows, create their own work, connect personal services, and publish allowed team resources |
Use Member by default. Give Admin access only to people who need to manage membership, billing, integrations, or organization-wide settings.
What a new member receives
After joining, a member can access resources that are public in that workspace, including:
- public agents;
- public workflows attached to those agents;
- workflow reference files shared through those public workflows;
- workspace-installed channels and integrations that support member connection.
An invitation does not transfer:
- another member's private agents or workflows;
- private chat history;
- personal connector credentials;
- a teammate's authorization or permission grants;
- ownership of another person's automations.
This boundary lets a team standardize how work is done without turning one person's account into a shared credential.
Send useful context with the invite
The product invitation gets the teammate into the workspace. A short message tells them what to do next:
I invited you to our team workspace.
After you join:
1. Switch to [workspace name].
2. Open the public [agent name] agent.
3. Connect [service] with your own account if prompted.
4. Run /[workflow-slug] with [example input].
5. Put the result in [shared destination] and send feedback in the same thread.
Use one workflow for onboarding. A long catalog without a first task makes it harder for members to understand the intended team pattern.
Manage pending invitations
In Settings → People, pending invitations are shown separately from active members. If someone did not receive or cannot use an invitation:
- confirm the invited email address is correct;
- ask them to sign in with the same email account;
- revoke an incorrect invitation and send a new one;
- check whether their organization requires an identity or email policy that blocks the invited account.
If the invitation was accepted by a different signed-in account, the recipient may see an account-mismatch message and a Switch account action.
Offboarding
Before removing a member, review resources and recurring work that depend on them:
- automations owned by that member;
- connected services used by those automations;
- private workflows the team still needs;
- shared deliverables that need a new owner.
Move or recreate required team processes before access is removed. Sharing a workflow does not automatically transfer the ownership and credentials behind a member-owned automation.
Send the recipient the Join a team workspace guide with the invitation. For Slack onboarding, continue to Use shared workflows in Slack.