Step by step, from the first key to single sign-on

Four guides written for the people who will actually do the work: the infrastructure team that publishes the gateway, the administrator who configures identity, and the developer who just wants Claude Code to work.

Step by step, from the first key to single sign-on

Each tutorial stands on its own and says up front who it is for and how long it takes. Read them in order for a complete rollout, or jump to the one you need today.

1. Every AI request through your gateway

For infrastructure. Publish the gateway, register provider keys once, block direct egress, create teams and budgets. About 40 minutes.

2. Connect Claude Code, Cursor and SDKs

For developers and workstation admins. Two variables, a managed settings file and the credential helper. About 15 minutes.

3. Sign in from the terminal with SSO

For developers. One command, one code confirmed in the portal, and no key on any laptop. About 5 minutes.

4. Configure SSO and device login

For administrators. OIDC provider, groups to teams, local accounts, device policy and directory sync. About 30 minutes.

Before you start

Prefer to delegate?: Every tutorial ends with a ready-made prompt for Claude Code or another AI agent with terminal access. The prompt asks you for what it needs, shows a plan, waits for your confirmation and then does the work. It never asks for the value of a provider key.

Nothing here is invented: Every screen, command and error message in these tutorials was captured from a real gateway. Where a feature has limits, the tutorial says so instead of hiding it.

  • A running appliance. If you do not have one yet, follow Getting started first.
  • An administrator account on the console, and the provider keys the company already uses.
  • For the SSO tutorials, an application registered in Entra ID, Keycloak or AD FS. The tutorial tells you exactly which values to copy.

About Atlasberg Platform

Atlasberg Platform is the control layer between a company and every AI model: each request is authenticated with a virtual key, filtered by policy and DLP, routed to the right provider and written to a hash-chained audit trail. It exposes an OpenAI-compatible API, so applications only swap the base URL.

The same artifact runs in Atlasberg Cloud, in your VPC, on-premises or fully air-gapped, and is priced by capacity and modules, never per seat.

This page is part of the official documentation. To talk to the engineering team, write to [email protected] or use https://atlasberg.com/contato. Answers come within one business day.

Agents: this page is also available as Markdown at /docs/tutoriais.md, or by requesting this URL with the header Accept: text/markdown. Index of everything: /llms.txt.