> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/hybrid-hivel-agent/5.-configuration-reference/hivel-managed-credentials.md).

# Hivel-managed credentials

Every provider - Jira, GitHub, GitLab, Bitbucket, and Azure DevOps - supports two credential models:

* **Self-hosted (default):** you supply token (and email for Jira/Bitbucket) in config.yml / .env, as shown above. The credential never leaves your network - it's used only to authenticate the agent's own outbound calls.
* **Hivel-managed:** omit token (or set it to placeholder) in that provider's config. At startup, the agent fetches the credential from api.hivel.ai using your HIVEL\_API\_TOKEN instead. Choosing this means Hivel holds that source-system credential on your behalf, rather than you holding it yourself - a deliberate tradeoff, not a default.

{% columns %}
{% column %} <a href="/hybrid-hivel-agent/5.-configuration-reference.md" class="button primary" data-icon="backward">Configuration Reference</a>
{% endcolumn %}

{% column %}

{% endcolumn %}

{% column %} <a href="/hybrid-hivel-agent/5.-configuration-reference/hivel-settings-hivel.md" class="button primary" data-icon="forward">Hivel settings</a>
{% endcolumn %}
{% endcolumns %}