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

# Team offboarding and access review

> Review members, invitations, shared links, connector access, billing, and usage when team access changes.

Use this checklist when someone joins, leaves, changes roles, or no longer needs team access.

<Note>
  Available controls can vary by plan, role, billing state, and account state. Team owners manage most team access and billing actions.
</Note>

## Offboard a team member

<Steps>
  <Step title="Open team settings">
    Go to **Settings > Team**.
  </Step>

  <Step title="Confirm your role">
    Make sure you are the team owner or have the controls needed to manage membership.
  </Step>

  <Step title="Review accepted members">
    Find the member whose team access should change.
  </Step>

  <Step title="Remove team access where available">
    Use the available member controls. Removed members no longer receive team plan access.
  </Step>

  <Step title="Review billing and usage">
    Check **Settings > Billing** and the usage card after the membership change has had time to refresh.
  </Step>
</Steps>

<Warning>
  Removing a member from a Babbily team does not delete content inside that person's separate account or connected apps.
</Warning>

## Review pending invitations

Pending invitations do not receive team access until accepted, but they are still worth reviewing.

Check for:

* Invitations sent to the wrong email.
* Invitations that are no longer needed.
* Duplicate invites.
* Teammates who need a resend.
* People who should be invited with a different email.

Cancel or decline invitations that are no longer needed, since pending invitations may affect billed seats before the invitee accepts.

## Review shared links

When team access changes, ask the owner or relevant teammate to review public share links.

Good checks:

* Does the shared thread still need to be public?
* Does it include customer, billing, connector, or confidential context?
* Should the thread be replaced with a cleaned-up summary?
* Does the audience still need access?

Shared links do not grant access to account settings, billing, connectors, or memory controls, but anyone with the public link can view the messages plus any attachments, generated media, citations, or other content included in the shared thread.

Public shared threads may also be discoverable in Google Search Results when public search visibility is enabled. Make links private when the thread no longer needs to be public.

## Review connector access

Connector access belongs to the account that authorized it. A team membership change does not automatically delete content inside connected apps.

Ask affected users to:

* Review connected apps in **Settings > Connectors**.
* Revoke access from the connected app if needed.
* Remove app permissions from the app's own admin settings when appropriate.
* Contact support if access cannot be managed from the UI.

## Review billing and usage

Team owners should check:

* Whether the member is accepted or pending.
* Whether billing controls show the expected team state.
* Whether API usage budget timing still matches the team plan.
* Whether a plan upgrade or downgrade is needed.

Billing and usage surfaces can take a short time to refresh after membership or plan changes.

## Access review cadence

For healthy team administration, review these regularly:

* Accepted members.
* Pending invitations.
* Billing owner and plan.
* Public shared chats.
* Connector authorization status.
* Team usage and low-budget warnings.

<CardGroup cols={2}>
  <Card title="Team admin guide" icon="users-round" href="/features/team-admin-guide">
    Manage team setup, invitations, billing visibility, and team usage.
  </Card>

  <Card title="Trust and data boundaries" icon="shield" href="/features/trust-safety-and-data-boundaries">
    Understand safe handling for chats, memory, connectors, sharing, and support.
  </Card>
</CardGroup>