> ## Documentation Index
> Fetch the complete documentation index at: https://docs.feedspace.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Members

> Tools for managing workspace team members and invitations.

Invite team members to collaborate within your workspace and manage their access. You can invite people as **Admin** (full access, apart from billing and deleting the workspace), **Editor** (can modify content), or **Viewer** (read-only access). The workspace **Owner** is a separate role that cannot be assigned through an invitation, but it does appear when you list team members.

## Available Tools

| Tool | Description | Try asking |
| - | - | - |
| `list_team_members` | List all team members with their roles (`owner`, `admin`, `editor`, `viewer`) and invitation status | "Show me all team members in my workspace" |
| `invite_team_member` | Invite a new team member by email as an Admin, Editor, or Viewer | "Invite [jane@company.com](mailto:jane@company.com) as an Editor to my workspace" |
| `reinvite_team_member` | Resend a pending invitation that has not been accepted yet | "Resend the invitation to the pending team member" |

<Note>
  Changing an existing member's role and removing someone from a workspace are not available through the MCP server. Both are supported in the [Feedspace dashboard](https://app.feedspace.io) under workspace team settings.

  `reinvite_team_member` only works while an invitation is still pending. Once it has been accepted, there is nothing to resend.
</Note>

## Roles and Permissions

| Permission | Owner | Admin | Editor | Viewer |
| - | - | - | - | - |
| View reviews | Yes | Yes | Yes | Yes |
| Create and edit reviews | Yes | Yes | Yes | No |
| Delete reviews | Yes | Yes | No | No |
| Manage forms | Yes | Yes | Yes | No |
| Manage team | Yes | Yes | No | No |
| Workspace settings | Yes | Yes | No | No |
| Billing and plan | Yes | No | No | No |
| Delete workspace | Yes | No | No | No |
| Transfer ownership | Yes | No | No | No |

Your role determines what the MCP server can do on your behalf. A Viewer authenticating through MCP gets read-only access, so write tools return a permission error.

## Which Team Member ID to Use

Team member operations are addressed by `unique_invitation_id`, the **string** identifier returned by `list_team_members`. The numeric `id` in the same response is not accepted; passing it returns a 404 "invitation not found".

Note that the workspace owner is returned by `list_team_members` with a `null` `unique_invitation_id` when they have no invitation record, so the owner cannot be targeted by these tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.