Configure a Capka Instance
Configuration starts with five decisions: who can join, which models they can use, where files live, what sandboxes may reach, and which agent actions require approval.
Recommended configuration order
- Create and secure the administrator account.
- Add one model provider and test it before adding more.
- Confirm persistent storage and your backup policy.
- Set allow, ask or deny rules for sensitive agent actions.
- Choose whether sandbox workloads may reach the public internet or internal services.
- Invite users only after the isolation and access settings have been reviewed.
Secrets and model keys
Capka can use a shared provider key for the instance or separate keys per user. Keep provider credentials in the instance configuration rather than in chat messages or workspace files. Users should receive only the providers and capabilities they need.
When a model is hosted outside your infrastructure, task content needed by that model can leave the server. Use a local model when the full workflow must remain inside your network.
Policies and connectors
Skills and MCP connectors can extend Capka with internal procedures and external services. Review the hosts, commands and requested secrets shown before installing a marketplace bundle. An update that broadens access should receive the same review as a new integration.