> ## 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.

# Admin rollout checklist

> Plan a team rollout for Babbily with access, billing, privacy, connectors, usage, training, and support readiness.

Use this checklist when you are introducing Babbily to a team or expanding access beyond a small pilot.

<CardGroup cols={2}>
  <Card title="Teams" icon="users" href="/features/teams">
    Set up a team workspace, invite members, and understand team usage.
  </Card>

  <Card title="Admin and procurement FAQ" icon="briefcase-business" href="/features/admin-and-procurement-faq">
    Review team, SSO, support, privacy, and procurement questions.
  </Card>
</CardGroup>

## Before inviting teammates

<Steps>
  <Step title="Confirm the owner">
    Choose the person who should manage billing, membership, and team setup.
  </Step>

  <Step title="Choose the plan">
    Review included API usage budget, team seat requirements, and billing expectations.
  </Step>

  <Step title="Define who should join">
    Start with the roles or departments that have clear Babbily use cases.
  </Step>

  <Step title="Prepare internal guidance">
    Tell teammates what types of data they may use in Personal and team workspaces, and what they should keep out.
  </Step>

  <Step title="Decide on Shared team memory">
    Choose whether useful team-chat context should be reusable by all members. Document what information is appropriate before the owner turns the setting on.
  </Step>

  <Step title="Pick connector boundaries">
    Decide which connected apps are appropriate for the rollout and who should authorize them.
  </Step>
</Steps>

## Recommended launch sequence

<AccordionGroup>
  <Accordion title="1. Set up the team">
    Create the team, confirm the team name, and review owner-only settings in **Settings > Team**.
  </Accordion>

  <Accordion title="2. Invite members">
    Invite teammates by email. Remind them to use the invited email address and complete onboarding before accepting the invitation.
  </Accordion>

  <Accordion title="3. Share a quickstart">
    Send teammates the [quickstart](/quickstart), [Teams](/features/teams), [prompting patterns](/guides/prompting-patterns), and [role-based getting started](/guides/role-based-getting-started) pages. Ask them to check the workspace pill before starting work.
  </Accordion>

  <Accordion title="4. Explain usage">
    Explain that AI work uses the plan's API usage budget and that heavier work such as research, media generation, and long model runs may use more.
  </Accordion>

  <Accordion title="5. Review data boundaries">
    Share guidance for memory, files, connectors, sharing, and sensitive information before teammates start uploading or connecting apps.
  </Accordion>

  <Accordion title="6. Establish support paths">
    Tell teammates who owns internal questions and when they should contact Babbily support.
  </Accordion>
</AccordionGroup>

## Suggested internal announcement

```text theme={null}
We are rolling out Babbily for AI chat, research, file work, and approved connected-app workflows.

Start here: [Quickstart]
Use Babbily for: [your approved use cases]
Do not use Babbily for: passwords, private keys, payment card numbers, government identifiers, or confidential data you are not allowed to process.
Questions: [internal owner or support path]
```

## Ongoing admin habits

* Review team members and pending invitations regularly.
* Cancel invitations that are no longer needed.
* Remind users to remove connected-app access when roles change.
* Review shared links and Library items when work changes ownership.
* Review team-wide shares and the Shared team memory setting.
* Revisit usage if the team approaches its plan budget.
* Update internal guidance when approved use cases change.

<Card title="Team offboarding and access review" icon="user-minus" href="/features/team-offboarding-and-access-review">
  Review members, invitations, shared links, connector access, billing, and usage when team access changes.
</Card>