Teams and Administration
One Capka instance can serve a team while keeping each person’s files and chats private. Administration focuses on access and operations, not reading user conversations.
What administrators manage
- User access and roles.
- Shared or per-user model credentials and available providers.
- Token spending by person.
- Allow, ask or deny rules for agent capabilities.
- Sandbox network access and installed integrations.
- Audit events for operational review.
What stays private
User workspaces, uploaded files and conversation histories remain separate. The administration panel exposes operational information such as roles and spend, not the contents of another person’s work.
A safe rollout sequence
- Start with a small group and one approved model provider.
- Test representative file workflows and confirm result downloads.
- Review connector permissions and sandbox network access.
- Set usage expectations and monitor token spend.
- Back up persistent instance data before expanding access or updating.