Account and settings

Everything in Kadmo belongs to an account: your company's workspaces, agents, playbooks, integrations, credit and settings. This page covers who is in the account and what they may do, the Team page where admins invite colleagues and manage the people who ask for work by request, every tab of the Settings page, and what an account's plan and trial mean in the app.

Accounts and roles

An account is created for a company and shared by everyone in it. Each person in the account has one of two roles:

Role	What it allows
Admin	Everything a User can do, plus: invite and remove members, change roles, create, archive and delete workspaces, deploy workspace configuration to agents, change settings and integrations, buy credit, set budgets, change the plan
User	Use the app: ask questions, start work, follow runs, review results. Settings pages open read-only, with a note that an account admin makes the change

An account always keeps at least one admin: the last admin can be neither demoted nor removed.

One account per person

A person belongs to exactly one account, the one they joined or created when they first signed in. There is no account switcher in the app. To move to another company's account, ask an admin of your current account to remove you, then accept the new account's invite by signing in with the invited address. An invite sent to someone who is still in another account stays Pending and is marked Already on another account on the inviting admin's Team page.

Members and invites

Open Settings at the bottom of the sidebar, then Team (under Account). The page lists everyone on the account, their role and when they were last active. Users see it read-only.

Invite a colleague

1. Under Invite a colleague, type their work address and pick the role: User or Admin.
2. Press Invite. Kadmo emails the invite so they know to sign in.
3. They join the account with that role the next time they sign in with that address. The invite is valid for 14 days.

The Invites table shows each invite's address, role, who sent it, when, and its status: Pending, Accepted or Revoked. On a pending invite:

• Resend sends the email again. Kadmo waits 60 seconds between two sends to the same address.
• Revoke ends the invite; it can never be used afterwards.

Message	Meaning
That person is already a member of this account.	Nothing to do
There is already a pending invite for that address.	Resend the existing invite instead
Just sent — wait ns before resending to this address.	The 60-second wait between sends
That invite is no longer active. Revoke it and send a fresh invite.	The invite expired; send a new one

Company domains and auto-join

An account can own its company's email domains. They are listed under Company domains and are managed by Kadmo staff. With Auto-join on, a colleague who signs in with a verified address on one of those domains joins the account automatically. With it off, only invited people can join, and a colleague who signs in uninvited is told Your team is already on Kadmo and asked to request an invite.

While new accounts open by invitation (see Getting started), joining works through an invite. Invite colleagues explicitly rather than relying on auto-join.

Change a role or remove a member

In Members, pick Admin or User in a member's row to change their role; the change saves at once. Remove takes a member off the account and ends their sessions. You cannot remove yourself, and the last admin cannot be removed or demoted.

People

People (N), between the invites and Members, lists who asks for work by request: a comment that mentions @kadmo on Jira, a Slack message or a Teams chat. For each person it holds their linked identities and an optional list of what they may start. Every member reads it; the controls are an admin's.

The rows:

• Every member of the account, shown with their e-mail address.
• Outside person: someone who asks in a tool but has no seat on the account, added here or by the Teams dialog.
• Paused marks a person who may start nothing.

Under the name are the linked identities as chips, Jira, Slack and Teams with the user's name, or No linked identity, and the person's list: May start the workspace's whole list, or Only: followed by the actions. With a linked Jira user, Kadmo knows that a request in that user's comment is theirs; a Slack link lets a notice reach them by direct message (My notifications). A Teams identity comes with the person added in the Teams dialog (Microsoft Teams).

Edit on a row opens the admin's controls:

Control	What it does
Link Jira user	Shown while the account has a Jira connection. Search the account's Jira users by name or e-mail and pick one
Link Slack user	Shown while a Slack channel with its bot is set up under Integrations. Search the Slack workspace by name, handle or e-mail; when the Slack app lacks the scope to list people or cannot be reached, type their member id (U…) or e-mail and press Link. Finding someone by e-mail needs the app's users:read.email scope
× on a chip	Unlinks that identity
All of the workspace's / Only these	The person's list. Only these ticks the playbooks and workflows they may start; Save list stores it. Only these with nothing ticked is refused: Pick at least one action, or choose All of the workspace's.
Pause / Resume	Outside people only. A paused person is offered nothing
Remove	Outside people only, on a second click (Click again to remove)

An identity belongs to one person: linking one that another person holds is refused with This identity is linked to another person. Add outside person, under the list, adds someone by name; link their identities next.

A person's list narrows each workspace's Started by request list for them and never adds to it: an action ticked here but not on the workspace's list is not offered. With All of the workspace's, nothing is narrowed. On a workspace set to Listed people only, a request is accepted only from an identity linked here.

Settings

Settings at the bottom of the sidebar opens the configuration level of the navigation: Workspaces, Files, Task setup, Automations, Integrations, BYOK, Guardrails and Chat agents under Configure; Roles, Workflows, Playbooks and Skill pack under Library; and Team and General under Account. Back returns to your workspace.

General opens the Settings page itself. It has ten tabs:

Tab	What it holds
General	Effort tiers and the default tier; the Goals Confidence bar
Agents	Each agent's workspaces and environment variables, and the defaults for new agents
Assistant	The assistant's name, persona, avatar, role and domains; MCP connections; Connect an MCP client
Models	Every Kadmo model, your favourites, which models the account offers, and the default model
Skill Pack Repository	The account's skill pack: its source, sync state, domains and readiness
Cloud	Firewall allowlist, connected providers, provisioning options, plugin marketplaces, SSH keys, recent activity
Logs	Webhooks and Cloud audit
Billing	Your plan, credit and billing status, and one line that reads the budgets
Appearance	System, Light or Dark for this browser; every member sets their own
My notifications	Which direct messages and e-mails reach you; every member sets their own

The model provider itself, Kadmo or your own key, is chosen under BYOK › Providers; Kadmo's models and the default model are on Models.

General

• Effort tiers are named presets for agent jobs. Each binds a Claude model and an effort level. Pick the default tier, which every agent job uses unless a workflow, a playbook, a step or the run picks another (see Effort tiers). You can rename a tier, change its Model and Effort, reorder it, delete it, or add one with Add tier. Press Save for the default tier.
• Confidence bar sets how sure an analysis must be before Goals' Decide step goes ahead on the agent's call instead of asking you.

Agents

One card per agent the account owns, with its status, the workspaces it hosts, and Environment Variables, the variables written to the agent machine. Save stores your changes, and Save & Apply also delivers them to the agent. Reboot restarts the machine, and Delete removes the agent. Admins also get RDP (a remote desktop shortcut) and SSH Key (the key download). Global Environment Variables are the defaults copied into every new agent. Agents you created keep their own values: edit an agent's card, then Save & Apply and Reboot to change it. Roles and effort per agent are set under Capabilities › Agents. The fleet itself is covered on Agents.

Assistant

The assistant that answers in Slack and in the app's chat:

Field	Meaning
Name	The name your team sees in Slack messages
Persona	The system prompt that shapes the assistant's voice and behaviour
Avatar URL	The picture shown with its messages
Active Role	The skill pack role that shapes its domain expertise
Domains	Which skill pack domains its role context includes

MCP Connections lists the tool sources the assistant, the Slack bot and MCP clients can use; switch each on or off, or follow Configure for one that is not set up yet. Connect an MCP client gives the address and the steps for Claude, Cursor, VS Code or Codex, and lists the tokens and connected clients you can revoke. See MCP overview.

Models

Every model Kadmo provides, under its provider, in the order of kadmo.ai/pricing. The first line names the default model: Ask Kadmo, Slack, Teams and Goals answer on it unless a thread picks another model, and agents run on their Kadmo agent app's model. The search filters by name, id and provider, and a count beside it reads how many models are available, off and Not served here yet.

Column	What it shows
★	Your star. Starred models lead every model list you open, after the default (see Pick the model); every member stars their own
Model	The model's name; the default is marked Default
Region	Where the model is served: EU or US
Context	The model's context window
Input / 1M, Output / 1M	The price per million input and output tokens, in euros (see How a call is charged)
Available	Whether the account offers the model. An admin flips the switch; a member reads Available or Off
⋯	An admin's row menu: Make default

A row is	When	What it shows
available	Kadmo serves it here, your plan includes its tier, and no admin switched it off	The star, the switch on, and Make default for an admin
off	An admin switched it off	The switch off and the row muted; the star is disabled, and an earlier star returns when the model is switched on again
locked	Your plan does not include its tier	The plan it comes with, instead of the switch (see What your plan decides)
not served here yet	Kadmo has not turned its route on	Not served here yet, on the row and on its provider's group

Make default sets the model Ask Kadmo, Slack, Teams and Goals answer on, and the first line and the Default marker move at once. The default's own switch cannot be turned off: make another model the default first.

Switching a model off keeps it out of every model picker on the account and refuses it for every lane: Ask Kadmo, Slack, Teams, Goals, chat agents, agents' jobs and a member's own client calling the LLM API read … is switched off on this account — pick another model. A thread already on it answers on the default and says so. Each change is confirmed in one line under the search. Only admins switch models and set the default; every member stars their own. The tab's foot links to Guardrails, where the switches' sum is read beside the account's other limits.

Skill Pack Repository

The account's skill pack: the knowledge agents read about your software, kept in git. The tab shows the pack's name and source (Portal default, a repository Kadmo hosts for you, or Own repo on GitHub, GitLab or Bitbucket), when it last synced (Sync Now), its clone URL (Copy, Download ZIP), and its counts of domains, modules and workflows with their average readiness. Account Domains lists each domain's modules, readiness, workspaces and repositories.

Under Repository Source an admin moves the pack to their own repository and chooses Portal write access: read-only (the default), Commit, or Pull request. Switching the source replaces the current pack, so you confirm the impact first. See Skill packs.

Cloud

Operations on the cloud accounts your agents run in. The credentials themselves are connected under Integrations.

Section	What it does
Firewall allowlist	The IP addresses and ranges that may reach agents over SSH and RDP through the agent firewall, per connection. Add my current IP adds yours. Saving replaces the whole list: at most 32 entries
Providers	Each connected provider with its status, the regions in use and when it was last validated; Check permissions
Provisioning options	Which machine sizes, profiles and regions the Create-Agent wizard offers, and its default. Reset to global clears the restriction
Claude Code plugin marketplaces	The marketplaces the wizard may install Claude Code plugins from
SSH keys	Which agents have a stored key, and how often it was fetched. Key material is never shown
Recent activity	The last five cloud, provisioning and firewall changes

Most of this tab is for admins; Users see it read-only. Setup per provider: AWS, Hetzner.

Logs

Webhooks lists incoming webhook events across all automations, with their status, the automation they matched and what they dispatched (Matched only filters). Cloud audit lists cloud connection, provisioning and firewall changes with who made them, and also the saves of the reporting settings and Kadmo's notices (Reporting), of the Started by request lists of workspaces and Slack channels, and of People and their linked identities. See Automations.

Billing

Plan & billing shows:

• Current plan with its state: on a trial, with the days left and the end date; trial ended; or active.
• Agents: how many the account runs against the plan's limit.
• Upgrade — book a call or Change plan, which books a call with Kadmo. Kadmo changes the plan after the call; Manage billing is not active.
• Kadmo credit: the balance, Buy Credits for admins, Where it went (usage By workspace, By lane, By model, or Threads and jobs), Credit added and Download CSV.
• Budgets: one line that reads the account's budget and the workspaces at their limit, linking to Guardrails, where budgets are set.
• Plans: the plan cards, with annual or monthly prices and an upgrade action for each.

Credit, budgets and the models are explained on Models and credit.

Appearance

System follows your device's setting; Light and Dark fix the theme. The choice applies at once, to this browser only.

My notifications

The direct messages in Slack and Teams and the e-mails that reach you when something needs you and when it is done; each follows the account's choice until you pick your own. See My notifications.

Plans

Every account is on one plan. The plan decides which models the account may use, how many agents it may run, and whether it may bring its own model providers. What each plan includes, and what it costs, is on kadmo.ai/pricing. How the plan shows in the app, in the model pickers, on Settings › Models and on the AI provider cards, is on Models and credit.

The trial

A new account starts on a trial. What the trial includes is on kadmo.ai/trial. The banner at the top of the app counts the days left. When the trial ends:

• the banner reads Your trial has ended — the portal is read-only. with Upgrade to continue;
• you can still open and read everything, but nothing new can be created or changed;
• an admin can still buy credit, and an Ask thread's owner can still revoke its share link;
• nothing you built is lost. Choosing a plan unlocks the account.

Related

• Getting started: sign-in and the invite-only rollout.
• Workspaces: what admins configure per workspace.
• Models and credit: credit, budgets and the model tiers.
• Integrations: trackers, git hosts, chat tools and cloud accounts.
• BYOK › Providers: Kadmo, your own keys and Voice.