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

# Manage members and permissions

> Invite teammates, organize teams, and keep administrative access intentional.

Workspace members are the people who can participate in this workspace. Teams
group those people for collaboration. Roles determine administrative access;
joining a team is not the same thing as becoming a workspace administrator.

**Before you begin:** open the intended workspace. An owner or administrator
should manage invitations and member changes. If the controls are unavailable,
ask a person who already manages that workspace.

## Invite a teammate

1. Open **Settings → Members**.
2. Choose **Invite team members** and enter the recipient's work email.
3. Review the role and any team selection presented by the invitation form.
4. Send the invitation and confirm that it appears as pending.
5. Ask the recipient to accept while signed in with the intended account.
6. Return to Members and confirm that the person is now an active member.

The last step is the useful completion check: a sent email alone does not prove
the person has joined the workspace.

## Manage a pending invitation

The invitation row has actions including **Resend invite**, copying the invite
link, and revoking the invitation. Use the pending row rather than repeatedly
creating new invitations for the same person.

* **The email was not received:** confirm the address, ask the recipient to check
  filtered mail, and resend the existing invitation.
* **The wrong person was invited:** revoke that invitation before sending another.
* **The person joined with another account:** compare the invited address and the
  account they are using before treating the missing workspace as a product error.

## Review member roles

The member list distinguishes Owner, Admin, and Member roles. For an eligible
member, the row menu offers **Change role to Admin** or **Change role to Member**.
The current UI does not use that action to change the owner or your own role.

Choose administrator access for people who need to manage the workspace, not
simply to make a record easier to find. If a person cannot see an item, first
check the workspace, view, and relevant access instead of promoting their role
as a shortcut.

## Organize teams

Use teams for stable working groups such as Delivery or Operations. A team
helps describe how people collaborate; it should have a purpose beyond grouping
everyone who happened to attend one meeting.

Removing someone from a team is different from removing them from the workspace.
Check which action you are taking and whether the person should retain general
workspace membership.

## Remove a member with a handoff

Before removing someone, review their ongoing tasks and other responsibilities
with the team. Reassign work or record the next person where necessary.

Use **Remove from workspace** on an eligible member and review the confirmation.
Afterwards, check the member list and the work you handed over. Do not assume
removal automatically completed or reassigned that person's tasks.

## How invitations relate to seats

Pending invitations do not consume paid seats. A recipient becomes an active
member after accepting; Kato updates subscription seat quantity for active
membership. Removing an active member reduces that quantity. Review
[Billing and plans](/documentation/billing-and-plans) for billing context.

## If the recipient still cannot join

Record the invited address, workspace name, whether the row is pending or
active, and any error displayed during acceptance. Share these details with
[support](/documentation/contact-support), without including passwords or sign-in codes.


## Related topics

- [Create your workspace](/documentation/create-your-workspace.md)
- [WhatConverts](/integrations/whatconverts.md)
- [Authentication and API conventions](/api-reference/authentication.md)
- [Google Docs](/integrations/google-docs.md)
- [Hand work off to a teammate](/recipes/handoff-work.md)