Skip to Content
kosemdocs
Concepts

Connections and access profiles

How organizations and projects connect kosem to GitHub, Google Cloud and AWS without stored keys, and slice each connection into shareable access profiles.

A connection gives kosem keyless trust to an external account: a GitHub App installation, a Google Cloud Workload Identity Federation trust (supporting up to 20 service accounts), or an AWS IAM OIDC trust (supporting up to 20 IAM roles). Connections keep no long-lived key of yours.

An access profile is a named, scoped slice of a connection — such as github/api_read or aws/deploy_staging — that defines the ceiling of short-lived credentials it can issue. Organization access profiles can be shared with projects (mirroring LLM Gateway's providers and models), and project access profiles can be granted directly to agents.

You find Connections, Access profiles and Secrets together under Access in the console, at both organization and project scope. Model providers, such as Anthropic and OpenAI, live under LLM Gateway (providers).

What connects

ServiceConnects withAccess profiles issue
GitHubAn installation of kosem's GitHub App on your account or organizationScoped installation access tokens (1 hour)
Google CloudWorkload identity federation: up to 20 service accounts trusting kosem, with no keyScoped OAuth access tokens (10 minutes to 1 hour)
AWSIAM OIDC federation: up to 20 IAM roles trusting kosem, with no keyScoped STS session credentials with session policies (15m to 1h)

How it works

  • The service must accept it first. kosem checks an installation or cloud trust before saving a connection's setup or changes.
  • Connections that stop working need attention. When an external provider refuses to issue credentials through a connection, kosem rechecks it in the background and marks it Needs attention, with the reason and how to fix it. Click Verify on its page to recheck immediately.
  • Share connections or share access profiles. An organization can share an access profile directly with projects (so teams receive ready-to-use scoped credentials without touching the raw connection), or share the underlying connection with projects so project teams can create their own access profiles within it.
  • A project's own connection is that project's alone. It isn't shared with other projects and is deleted with the project. A policy, Turn off projects' own connections (connections.projectConnectionsDisabled), keeps projects from connecting accounts of their own; connections added before keep working.
  • A GitHub installation belongs to one connection across an organization and its projects.
  • Native environment authentication. When a project access profile is granted to an agent, kosem authenticates git, gh, aws, gcloud and Google Cloud / AWS SDKs automatically inside the agent's environment. Revoking the grant invalidates active credentials immediately over the environment tunnel.
  • A connection in use can't be deleted until its access profiles are deleted, unless you force deletion, which deletes its access profiles and revokes their agent grants.

Why it works this way

  • One trust relationship, many scoped profiles. Connect a GitHub org, GCP pool or AWS OIDC provider once, then carve out narrow read-only and write access profiles for each team and workflow.
  • Ceiling plus narrowing. Every access profile sets a hard ceiling; an agent grant can narrow it further (such as fewer repositories or a shorter TTL), and runtime requests can only narrow further still.
  • No keys where there needn't be. Workload identity federation and GitHub App installations eliminate long-lived static credentials to leak or rotate.

Who can do what

ToYou need
See connections and access profilesAny basic role, or Connection Viewer (roles/connections.viewer)
Create, change, verify, share and delete connections and access profilesOwner or Connection Admin (roles/connections.admin)
Create access profiles backed by a connectionOwner, Connection Admin or Connection User (roles/connections.user)
Issue short-lived credentials from an access profile or grant it to an agentOwner, Connection Admin or Access Profile Accessor (roles/connections.accessor)
Revoke an access profile grant from an agentOwner on the agent, Owner or Agents Admin on the project, or Connection Admin (IAM admin) on the profile

On this page