Skip to main content

Some screenshots show mcp-s.com, which some existing organizations still use. New organizations use withwillow.ai. Copy the URLs shown in your own organization.

Users

Users

The Users page lists everyone in your organization. It is where you add people, put them in groups, and check what any one person can actually reach.

Willow grants access through groups, not through individual users. A user on this page has access to a resource because a group they belong to has it. So most work here is really two steps: get the person into Willow, then get them into the right groups.

What you can do here​

  • Add users one at a time, or import many from a CSV
  • Send invites
  • Change which groups a user belongs to
  • See every MCP server, toolkit, skill, and guard a user can reach
  • Remove users

The users table​

The count above the table shows how many users you have. Users your identity provider has deactivated through SCIM are hidden from the table and the count by default. Turn on Show deactivated in the toolbar to list them again.

ColumnWhat it shows
NameThe user's display name.
EmailThe user's primary email address. This is their identity in Willow and changes only through Email aliases, by making another address primary. A +N badge counts the user's aliases.
GroupsHow many groups the user belongs to.
MCPsThe user's MCP servers.

Name, Email, and Groups are sortable. Use Search users to find someone by name or email, and the All MCPs filter to narrow the list by MCP server.

note

The MCPs column does not list every MCP server a user is entitled to through their groups, and a dash here does not mean the user has no access. To see what a user can actually reach, use View Access.

Add a user​

  1. Select Add User.
  2. Enter the user's Name and Email.
  3. Select Send Invite if you want Willow to email the user now. Leave it clear to create the user without notifying them, and invite them later.
  4. Select Create.

The new user has no group memberships yet, so they have no access to resources. Assign their groups next.

Import users from a CSV​

Use Import Users when you are onboarding a team rather than a person. The import can place users in groups as it creates them, which saves assigning groups one by one afterwards.

  1. Select Import Users.

  2. Select Download CSV Template to start from the expected format.

  3. Fill in one row per user:

    ColumnRequiredWhat it holds
    EmailYesThe user's email address.
    Full NameYesThe user's display name.
    GroupsNoGroup names, comma-separated. Wrap the field in quotes when listing more than one.
  4. Select Upload CSV File and choose your file.

Use the exact group names from your Groups page in the Groups column.

Assign groups​

  1. Find the user and open the ... menu at the end of their row.
  2. Select Edit Groups.
  3. Select the groups the user should belong to. The groups they already belong to are listed first. Use the search box to filter a long list.
  4. Select Done.

Groups tagged SCIM are managed by your identity provider through SCIM, so you can't change them here.

Access follows immediately from group membership. To decide which groups to build in the first place, see Make MCP Servers, Toolkits, Skills, and AI Tools Available to Users.

Check what a user can access​

When someone reports missing access, or you want to confirm a change landed, use View Access rather than reading group memberships and working it out yourself.

  1. Open the ... menu on the user's row.
  2. Select View Access.

The page shows the user's group memberships, counts of the MCP servers, toolkits, skills, and guards they can reach, and two views:

  • Table: a card per resource type, listing what the user can reach. MCP servers also show connection status and call counts.
  • Map: a diagram tracing the user to their groups, and each group to the resources it grants. Use this to see why a user has something, which is the faster answer when the access is unexpected.

Email aliases​

A user can have more than one email address, for example when your identity provider uses one domain and Slack uses another. Willow treats every address as the same user: they can sign in with any of them, and Slack, the API, and logs resolve any of them to that user. Mail goes to the primary email.

  1. Open the ... menu on the user's row and select Edit.
  2. Under Emails, enter the address and select Add.
  3. To change which address is primary, select Make primary next to it.
  4. Select Save.

No two users can share an address, as a primary email or an alias. If your identity provider sends more than one email over SCIM, Willow keeps the aliases in sync. Aliases you add by hand stay when the identity provider syncs. To sync a secondary email from Okta, see Sync a secondary email.

Row actions​

The ... menu on each row holds:

ActionWhat it does
View AccessOpens the access page described above.
EditChanges the user's display name. With Email Aliases on, it also edits the user's emails.
Edit GroupsChanges group memberships.
Send an InviteEmails an invite to the user. Use this for users created without one.
Refresh KeyIssues the user a new key, replacing their existing one.
DeleteRemoves the user from your organization.
caution

Refresh Key and Delete are both destructive, and Willow marks them as such in the menu. Replacing a key invalidates the previous one, so any client still configured with it stops working until the user reconnects with the new key.