Team and workspace

Every AskAnyDocs user works inside a team context. A team can be a personal workspace for one user or a shared workspace with multiple members. The active team determines which bots, resources, limits, and API data you can access.

Personal and shared workspaces

When you start using AskAnyDocs, you may work in a personal team by default. This is enough for testing, building a first bot, or managing a small documentation assistant on your own.

Shared teams are useful when multiple people need to manage the same bots. For example, a product marketer might manage website copy, a support lead might review conversations, and a developer might handle widget installation or API usage.

Team members

You can invite teammates, review members, and adjust access from the team section in the app. Add people who need to work with bot settings, resources, conversation review, or account-level configuration.

Common team roles include:

• owner or administrator for billing and workspace settings
• support lead for reviewing conversations and escalations
• content manager for improving indexed documentation
• developer for widget installation and API integration
• marketing or product team member for brand and messaging review

Keep team access current. Remove people who no longer need access, especially if they worked on temporary implementation or content projects.

Team settings

The team settings page lets you update workspace-level details such as the team avatar and shared presentation details. These settings help members recognize the current workspace, especially if they belong to more than one team.

Use clear team names when managing multiple brands, clients, or environments. A name such as Acme Production or Acme Docs Test is easier to understand than a generic workspace label.

Why the active team matters

Bots, usage, and limits are associated with the current team context. When you switch teams, you switch into that team's workspace and resources.

This affects:

• which bots appear in the dashboard
• which resources and files are available
• which conversations and messages you can review
• which plan limits apply
• which API keys and external API data are available

If a bot or resource seems to be missing, check that you are viewing the correct team before changing settings.

Collaboration tips

For production bots, agree on a simple ownership process. Decide who approves new knowledge sources, who reviews conversations, and who updates documentation when users ask repeated questions.

A clear workflow prevents duplicate content and reduces the chance that outdated documents are indexed by mistake.

Related articles