Skip to main content
A few things need to exist in the Komodor Agentic Operation Platform (KAOP) before an agent can do anything useful. This page lists them, says who can provide each, and tells you which ones you can skip depending on what you plan to do. It takes a few minutes and saves you hitting a wall halfway through a tutorial.

​
Access to a workspace

A workspace is your team’s isolated space for agents, runs, integrations, and members. Everything you create belongs to one.
1

Get your workspace URL

Your Komodor contact provides it. It is also the base host for every API example in these docs.
2

Sign in with SSO

Authentication goes through your identity provider — there is no separate password. First-time access is provisioned as you sign in. See Signing in.
3

Confirm you have the right role

Reading runs, creating agents, and managing access are separate permissions. If a screen or action appears locked, your role does not grant it — see Roles & permissions.
If you belong to more than one workspace, switch between them from the sidebar.

​
At least one connected system

An agent with no access can reason but cannot observe or act. Connect one system before your first real run — the one whose data you actually want an agent looking at. Start with Integrations overview to see the catalog and how a connection becomes tools an agent can use.
Connecting a system usually needs credentials your platform or security team holds. Worth requesting before you start, not mid-tutorial.

​
The SDK — only if you are authoring agents

Two paths through Build, and only one of them needs local tooling:
  • Deploying a Komodor-built agent — nothing to install. Everything happens in the console. See Use specialized agents.
  • Authoring your own agent — you write a worker in Python or Go and run it against the control plane. See Build from scratch.
For the Python path:
Set the workspace host once and the API examples in these docs work as written:

​
Programmatic access — only if you are automating

Driving KAOP from CI, a script, or your own service needs a credential:
  • An API key for a person-scoped or automation-scoped token — see API keys.
  • A service account when the automation should have its own identity rather than borrowing yours — see Service accounts.

​
Quick check

You are ready when all of these are true:
  • You can sign in and land on your workspace
  • You know which role you hold
  • At least one system is connected
  • The SDK is installed, if you plan to author agents
  • You hold an API key, if you plan to automate

​
Next steps

Concepts & glossary

The vocabulary everything else assumes.

Build your first agent

Create and run one, end to end.

Onboarding

The guided checklist that tracks your setup.

Interfaces

Console, API, SDKs, MCP, Slack — and when to use each.