> ## 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 and procurement FAQ

> Answer team, billing, SSO, privacy, support, connector, and access questions before buying or expanding Babbily.

Use this FAQ when you are evaluating Babbily for a team, preparing an internal purchase, or answering admin questions.

## Team and access

<AccordionGroup>
  <Accordion title="Who manages a Babbily team?">
    Team owners manage the workspace identity, invitations, member removal, Shared team memory, plan changes, billing, and team usage controls where available. Team members can use the team plan but may not see owner-only controls.
  </Accordion>

  <Accordion title="Can one account have Personal and team workspaces?">
    Yes. Every account has a Personal workspace, and accepted team memberships add team workspaces to the account menu. Chats, Saved Prompts, Library items, and memory stay with the workspace where they were created.
  </Accordion>

  <Accordion title="How many people are needed to create a team?">
    Team setup requires at least three people total, including the owner. Pending invitations do not receive team plan access until accepted, but may affect billed seats until accepted, declined, or canceled.
  </Accordion>

  <Accordion title="What happens when someone is removed from a team?">
    Removed members stop receiving team plan access and lose membership-gated access to team shares. Removing a member does not delete content inside that person's Personal workspace or connected apps.
  </Accordion>

  <Accordion title="Can teams use SSO?">
    Team plan cards may list SSO integration. Availability and setup can depend on the plan and account, so contact support if SSO is a procurement requirement.
  </Accordion>

  <Accordion title="Are team analytics available?">
    Team plan cards may list team analytics or usage tracking. Exact visibility can depend on your plan, account state, and role.
  </Accordion>
</AccordionGroup>

## Billing and support

<AccordionGroup>
  <Accordion title="How are team plans billed?">
    Team plans use seat-based billing with a three-person minimum, including the owner. Team owners manage subscription and billing controls. Team members may have limited billing visibility.
  </Accordion>

  <Accordion title="Can an individual plan stay active with a team plan?">
    Yes. Individual and team plans can coexist, and joining or creating a team does not automatically cancel an individual subscription. A team owner switches to the team workspace they own before changing that team's plan.
  </Accordion>

  <Accordion title="What does API usage budget mean for teams?">
    Accepted team members receive the team plan's included API usage budget and follow the team plan's reset timing.
  </Accordion>

  <Accordion title="Is priority support available?">
    Some paid and team plan cards list priority support. Team plan cards may also mention a dedicated account manager. Contact support if you need to confirm support coverage for your account.
  </Accordion>

  <Accordion title="What details help with procurement questions?">
    Include the plan you are considering, estimated number of accepted users, billing owner email, SSO needs, support expectations, privacy questions, and any required timeline.
  </Accordion>
</AccordionGroup>

## Data, privacy, and connectors

<AccordionGroup>
  <Accordion title="Where can I review privacy terms?">
    Open **Settings > Privacy** or visit the Babbily Legal Zone linked from the product. The privacy page summarizes how Babbily handles conversations, data selling, deletion requests, safety, account communication, and optional features.
  </Accordion>

  <Accordion title="Does Babbily train on conversations by default?">
    Babbily's privacy settings state that Babbily does not use your chats to train generative models by default unless you have given explicit permission.
  </Accordion>

  <Accordion title="Who controls connected-app access?">
    Connector access belongs to the account that authorized it and is also limited by the connected app's own permissions. Workspace admins should manage app permissions from the connected app when needed.
  </Accordion>

  <Accordion title="How does Shared team memory affect a data review?">
    The team owner can enable Shared team memory from **Settings > Team**. When enabled, useful facts from team-workspace chats can become shared context for current members. Personal Memory Profiles remain separate. Decide what team-wide context is approved before enabling the setting.
  </Accordion>

  <Accordion title="Can teammates share work without making it public?">
    Yes. Supported team-workspace chats and saved media can be shared read-only with specific teammates or everyone in the team. Access depends on current membership and is separate from public share links.
  </Accordion>

  <Accordion title="Can admins remove connector access for a departing teammate?">
    Team membership changes do not automatically delete connected-app content or permissions. Ask affected users to review **Settings > Connectors**, and use the connected app's admin settings when your organization needs to remove app access.
  </Accordion>

  <Accordion title="What should not be shared in Babbily?">
    Do not enter passwords, verification codes, API keys, private keys, payment card numbers, government identifiers, raw connected-app credentials, or confidential data you are not allowed to process in Babbily.
  </Accordion>
</AccordionGroup>

<CardGroup cols={2}>
  <Card title="Teams" icon="users" href="/features/teams">
    Switch workspaces, share with teammates, and understand Shared team memory.
  </Card>

  <Card title="Team admin guide" icon="users-round" href="/features/team-admin-guide">
    Manage identity, roles, invitations, memory, billing, usage, and troubleshooting.
  </Card>

  <Card title="Billing FAQ" icon="wallet" href="/features/billing-and-plan-changes-faq">
    Understand plan changes, resets, and team billing.
  </Card>

  <Card title="Privacy and data" icon="shield-check" href="/features/privacy-and-data">
    Review practical data controls for everyday use.
  </Card>
</CardGroup>