Workspace Setup

Most infrastructure setup is handled by Wato. Workspace admins configure the parts of Wato that affect their organization: users, teams, directory groups, connectors, permissions, and review visibility.

Invite users

Use this when you want teammates to join your Wato workspace.

1. Go to Admin → Users.
2. Click Invite user.
3. Enter the user's email address.
4. Choose their workspace role.
5. Send the invite.

After the user accepts, they can sign in to Wato. They still need team access before they can see private team memory, use team MCP tools, or review team-specific activity.

Use this workflow to add teammates, assign workspace admins, and keep workspace access separate from team memory access.

Create teams

Use this when you want to separate memory, MCP tools, review queues, and traces by function or group.

1. Go to Admin → Teams.
2. Enter a team name.
3. Choose a visibility setting:
   • Private: only members can access the team.
   • Requestable: users can discover the team and request access.
   • Public: visible more broadly inside the workspace.
4. Click Create team.

After the team is created, open it from Teams → [Team]. The team will have its own pages for memory, connectors, context, traces, and review workflows. Common teams include Sales, Customer Success, Support, Product, Engineering, and Leadership.

Configure team access

Use this when you want to control who can see a team's memory and who can manage the team.

1. Go to Admin → Teams.
2. Click the team you want to manage.
3. Add users by email.
4. Choose each user's team role:
   • Member: can access team memory and approved team tools.
   • Team admin: can manage team membership and team-level settings.
5. Save the change.

Team membership controls access to team memory. A user can belong to the workspace without automatically seeing every team's private memory.

Connect your directory

Use this when your organization wants Wato access to follow your identity provider or company directory.

1. Go to Admin → Directory Sync.
2. Connect your identity provider.
3. Sync users and groups.
4. Map directory groups to Wato teams.
5. Choose the role synced members should receive in each team.
6. Review the mapping before enabling it.

After directory sync is enabled, changes in your directory can update Wato membership. For example, adding someone to an "Engineering" group can add them to the Engineering team in Wato.

Approve connectors and MCP tools

Use this when you want a team's agents to access external systems through MCP.

1. Go to Admin → Connectors to manage available connectors for the workspace.
2. Choose a connector, such as GitHub, Linear, Google Drive, or a custom MCP.
3. Approve the connector for the workspace or for specific teams.
4. If the connector requires authentication, connect the required account.
5. Open Teams → [Team] → Connectors.
6. Select the connector.
7. Review the available MCP tools.
8. Allow or block specific tools for that team.

This lets admins approve a connector without automatically allowing every tool inside it. For example, a team might be allowed to search CRM records but not update admin settings.

Review activity

Use this when you want to see what agents and MCP tools are doing.

1. Go to Traces for workspace-level activity, or Teams → [Team] → Traces for team-specific activity.
2. Open a trace to inspect the details.
3. Review which MCP tool was called, who called it, which team context was used, what input was sent, whether the call succeeded or failed, and when it happened.

Use this workflow to debug agent behavior, monitor MCP usage, support compliance reviews, and investigate failed tool calls.

Review memory changes

Use this when users or agents submit memory drafts for approval.

1. Go to Teams → [Team] → Memory → Review.
2. Open a pending proposal.
3. Review the proposed Markdown changes.
4. Check the mergeability status:
   • Ready to merge: the proposal can be approved.
   • Has conflicts: the author must resolve conflicts first.
   • Mergeability unknown: refresh or reopen the review before merging.
5. Click Merge when the proposal is ready.

After the proposal is merged, the change becomes trusted team memory and can be retrieved by agents through Wato MCP.