---
title: "Connect Integrations and Credentials Safely | Agent Barn"
canonical: "https://agentbarn.dev/guides/integrations-and-credentials"
pubDate: "2026-08-25T00:00:00.000Z"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Choose provider credentials, shared credentials, OAuth access, and least-privilege runtime materialization."
tags: [Product guide, Organization administrators and operators, Agent Barn]
categories: [Guides]
---

# Connect Integrations and Credentials Safely

Agent Barn validates and encrypts provider-specific credentials, then materializes only the configuration and Skills needed by an Agent at start. Credential classes have distinct owners and lifecycles.

## Guide details

- Reference: GD-04
- Type: Product guide
- Audience: Organization administrators and operators

## Supported provider families

Current provider contracts cover GitHub, Jira, Confluence, Bitbucket, Gmail, Google Calendar, Google Sheets, Zoho Mail, Zoho Calendar, Firecrawl, Slack, and Pipedrive. Each Agent can have at most one credential source per provider.

## Choose Agent Secrets or Shared Credentials

Agent Secrets belong to one Agent. Shared Credentials belong to an Organization, are managed by Owner/Admin, and can be attached by Members. Manual-entry providers supported for sharing are GitHub, Jira, Confluence, Bitbucket, and Zoho Mail. OAuth-backed Google providers are not shared in the current contract.

- A provider cannot use both a Shared Credential and per-Agent secret on the same Agent.
- Shared Credential names are unique within an Organization.
- A Shared Credential cannot be deleted while a non-deleted Agent references it.
- Read APIs expose labels and providers, never credential contents.

## Google OAuth and Slack setup

Google authorization uses signed, short-lived state and requests provider-specific offline scopes. Gmail is read-only; Google Sheets uses value read/write plus metadata-only Drive access for discovery. Per-user Slack configuration tokens automate app creation, while each Slack Agent still has its own bot and app tokens.

## Runtime materialization

At Agent start, the service decrypts provider payloads, builds the `aai-cli` secret store and configuration, injects provider environment, mounts eligible Skills, and appends integration policy to the rendered Template. Firecrawl can be platform-wide, with an optional per-Agent override.

## Least-privilege checklist

Prefer read access before write access, restrict accounts to intended repositories or spaces, add one capability at a time, and test both an allowed resource and a resource that should remain inaccessible. Treat encryption-key rotation as a credential migration.