Integrations settings
Manage organization credentials and org-wide Jira configuration.
What this means
Integrations settings are where an organization connects external providers that Bilbis needs. This includes LLM providers, Git providers, Jira, and other provider credentials.
This is the place where admins manage the credentials described in BYOK.
What you see depends on your role:
- Owner / Admin - the full management view: add, validate, and delete credentials, plus the org-wide Jira card. Everything below applies.
- Developer / Viewer - a read-only Configured providers summary card listing each provider as Configured or Not configured. No labels, no last-four digits, no buttons. Ask an admin to add or rotate credentials.
Before you start
You need organization access. In most organizations, credential management should be handled by owners or admins.
Before creating your first useful pipeline, add at least:
- one LLM provider credential, such as Anthropic or OpenAI,
- one Git provider credential, such as GitLab or GitHub,
- a product,
- a repository.
Credential providers
The generic credential form supports these providers:
| Provider | Common use |
|---|---|
| Anthropic | LLM provider for agent work. |
| OpenAI | LLM provider for agent work. |
| GitLab | Git provider for cloning, branching, pushing, and merge requests. |
| GitHub | Git provider for cloning, branching, pushing, and pull requests. |
| GitHub App | Reserved for GitHub App-style credentials. |
| Resend | Email provider credential for organizations that bring their own email key. |
| Cloudflare | Cloudflare credential for supported infrastructure workflows. |
Jira is configured through the dedicated Jira card, not the generic credential form, because Jira needs both a credential and Jira configuration in one flow.
Read-only summary view
If your role is Developer or Viewer, the page replaces the full management table with a flat Configured providers card. Each provider in the table above shows a status badge:
| Status | What it means |
|---|---|
| Configured | At least one credential exists for this provider in the org. |
| Not configured | No credential exists. |
The summary view never shows labels, last-four digits, validation timestamps, or any mutation buttons. Ask an admin to add or rotate credentials. Admins are typically the org Owner and any users with the Admin role.
The Jira card is also hidden in the summary view because it manages credentials and config in the same flow.
Add a credential
- Open Settings.
- Select Integrations.
- Select Add credential.
- Choose a provider.
- Enter a clear label, such as
Production Anthropic. - Paste the API key or token.
- Save the credential.
After saving, Bilbis validates the credential so the row can show whether the provider is reachable.
Credential status
| Status | What it means |
|---|---|
| Not validated | The credential has not been checked yet. |
| Reachable | Bilbis successfully validated the credential. |
| Failed | Validation failed. Hover or open the failure details to see the provider error. |
The row also shows when the credential was last validated and, when available, the last four characters of the stored key.
Validate or delete a credential
Use Validate when you want to check whether a credential still works.
Use Delete only when you are sure the key is no longer needed. Pipelines that depend on a deleted key can fail until the credential is replaced.
Jira configuration
The Jira card manages organization-wide Jira setup. It covers:
- Jira URL.
- Jira type.
- auth email.
- token configuration.
- status mapping.
- project mapping.
- webhook secret.
Use this card when Jira tickets should create pipelines or when MRs/PRs should link back to Jira.
Product-specific Jira settings may override the organization-wide configuration for a product.
Problems and fixes
| Problem | What to check |
|---|---|
| No credentials appear | Add at least one LLM provider and one Git provider before dispatching a pipeline. |
| Validation fails | Check that the token is active, has the right scopes, and belongs to the expected provider account. |
| A pipeline fails after deleting a credential | Add a replacement credential, then retry the pipeline. |
| Jira validation fails | Configure Jira through the Jira card so the URL, token, auth email, and Jira type are saved together. |
| A provider is missing from the picker | Jira intentionally uses its own setup card. Some providers may be reserved for later workflows. |