Workspaces, Teams & Permissions
As your use of Bothive grows, workspaces keep things organized and roles keep them controlled.
Workspaces
A workspace groups related bots, integrations, and keys — think one per project, client, or team. Switch between them to keep contexts separate. Create and manage them under Workspaces.
Inviting your team
Under Team, invite teammates by email. They join the workspace and can collaborate on the bots and workflows inside it — no need to share logins or keys.
Roles & permissions
Not everyone should be able to do everything. Under Roles & Permissions, assign each member a role that scopes what they can access and change — for example, who can create API keys, edit bots, or manage billing.
Keys per workspace
Generate API keys scoped to a workspace so external apps only reach that workspace's bots. Rotating or revoking a key affects just that surface.
Good practices
- One workspace per project keeps keys, integrations, and usage cleanly separated.
- Give teammates the least access they need.
- Review members and keys periodically; remove what's unused.
Next steps
Use the test pane to iterate quickly. Every change you make is live — no need to save first.
API keys are shown only once. Store them securely and never commit them to version control.
Test your bot with edge cases before deployment. Try empty inputs, long messages, and special characters.
Chain multiple specialized bots in a workflow for better results than one general-purpose bot.