Skip to main content

Model accounts

A model account is the AI account a runner signs in as to do a task's work, for example a Claude Code subscription or an API key. AI Accounts lists the accounts you can see and how much of each one's quota is used.

Open it from the sidebar: select Directory, then AI Accounts. The screens below were taken with the org admin role: the Enabled column, the row menu's changes, Export and Share require the org admin role, or the permissions named beside them. Every member may select Add account to bring an account of their own; a member without the org admin role adds it as a personal account.

An account authenticates in one of two ways:

  • Subscription (OAuth): a person signs in to a subscription on a node. The account reports its plan's quota.
  • API key: a key Jaah stores for you. No sign-in, no node and no quota: it's billed per token.

The list​

The AI Accounts list: the column headers Account, Sessions, Enabled, Provider, 5h and 7d over a subscription account with its plan chip and quota, an API-key account with its API key chip, and a subscription with the personal chip

Share, Import and Add account sit at the right end of the tab strip; with an account open, Import hides and Add account reads Add. See Share subscriptions between nodes and Import an account.

A header row names the columns. Each row shows, from left to right:

ItemMeaning
Round mark● available, ▲ quota nearly used up, ✕ failing, ⊘ disabled, ◌ initializing: just signed in, and no node has reported it yet.
▶Opens the account's nodes, or an API-key account's details, under the row. See Nodes and details.
AccountThe account's name, then the subscription's sign-in email and its plan, or an API key chip. Hover the name to read the account's description. Select it to open the account's details.
SessionsHow many runners use the account now, and how many are busy. — when none. Hover the number to see where they run.
Enabled✓ when the account is enabled, Disabled when not. Point at it to see what selecting it does, ⊘ Disable or ✓ Enable; select it to switch. Requires the org admin role. Shown in a wide window.
ProviderThe agent the account runs, for example Claude Code.
5hHow much of the 5-hour quota is used, and the time until it resets.
7dHow much of the 7-day quota is used, and the time until it resets. It is the first column to go in a narrow window.
⋯The row menu.

The two quota columns are named after the quota windows of the accounts listed when they all share them, and 5h and 7d otherwise; hover a figure to read its own window. A quota cell shows — when it has no data: no reading yet, or no quota at all, such as an API-key account. Hover it for which. A ⚠ beside a figure means the reading is old.

The identity can carry these chips:

ChipMeaning
no keyAn API-key account with no key stored.
initializingThe account was signed in during the last few minutes and no node has reported it yet. It turns to the account's real state once a node does, or after five minutes.
no credentialsThe account has never been signed in.
rejectedA runner found the provider refusing the account's sign-in, and it is out of rotation. Hover it to read the provider's reason.
limit hitA runner hit the account's limit, and it is out of rotation. Hover it to read why.
explicit onlyAuto-assign is off: the account runs only tasks that pick its provider.
personalOne member's own account. Hover it to see whose.
re-login in timeThe sign-in expires soon. When you may add accounts, select it to sign in again now.
Shared via NodeLinkNodes read the sign-in from that NodeLink's token folder. Select it to open the NodeLink.

A ⚠ after the name means one of the account's nodes needs attention, such as a sign-in. Hover it to see which. Hover the name of an account signed in nowhere to read why and what to do. When you may sign it in, the row says Not signed in on any node yet., or Its node was removed. when the node holding its sign-in was deleted; open it to see the same line with a Sign in or Add to node link.

When you can see no account, the page says No runner accounts visible.

A member whose role can't view every account's status sees only the accounts they may use, read from the account itself: its provider and its 5h and 7d quota, with no sessions and no node rows. The round mark then reads:

MarkMeaning
●ready
◌signing in: signed in during the last few minutes.
✕sign-in rejected
▲usage limit: the account's limit or credit is used up.
⊘disabled
!sign-in not finished: the account was added but never signed in.

With none, the page says No accounts yet. Add your own., or Your role can’t view account status. Ask an admin for access. when you may not add one.

Nodes and details​

Select ▶ beside the name to open the account under its row. Select ▼ to close it.

An open subscription account: one node row under it with its server icon, name, Local chip and the state ok

A subscription account lists one row per node it has been seen on. Each node row shows the node's quota, the provider and its state:

MarkMeaning
◐provisioning: the node is still being set up and hasn't read any account yet. Nothing to do.
●Signed in, with a quota reading: the state reads ok.
○The account isn't on this node.
!The account has no sign-in on this node, or the node can't read it: can't read credential. Hover it to see where the node looked.
✕The sign-in was refused.
?Signed in, but no quota reading yet: no reading. It is unknown, not broken.
◌Syncing…: signed in on another node that shares this node's NodeLink. It shows up at the node's next check.

Beside each node's name, Shared means it reads the sign-in from a NodeLink; Local means from its own folder. A node that doesn't report it shows neither.

After about two checks, a node still syncing shows Not synced, with the reason on its hover, such as The node reports it isn't mounted. A node whose NodeLink isn't mounted shows that at once.

When the node knows why it has no reading, the state names it instead. Each is retried on the next check:

StateMeaning
refresh lockedThe sign-in is being refreshed elsewhere.
refresh failedRefreshing the sign-in failed for now.
usage check failedThe provider didn't return the quota.

When the account needs signing in on a node, the state shows Login if you may add accounts, and missing or needs login otherwise. Two more states can't be fixed by signing in again: Billing (the subscription needs payment) and Seat (the seat is suspended; an administrator must fix it).

Open, an initializing account whose nodes haven't reported it yet says Initializing… and lists no node rows, a subscription no node has reported yet says No node has reported yet, and one with no node to sign in on says No node to sign it in on yet., with a New node link (requires the org admin role). An API-key account says The key is write-only: rotate it from Edit. It runs on any node.

The row menu​

The row menu of a subscription account: Add to node, Edit, Disable and Delete

  • Sign in signs in an account that is signed in nowhere yet.
  • Add to node signs the account in on another node. Not offered while the account is initializing.
  • New node opens the form to add a node, when there is no node to sign the account in on. Requires the org admin role.
  • Re-login signs a subscription in again after its sign-in was refused. See Sign an account in again.
  • Edit opens the account. See An account's details.
  • Disable stops runners from using the account. Enable turns it back on.
  • Delete removes the account for good: its running sessions stop, and its sign-in is removed from every node and from the shared folder. A node that is offline removes it when it next connects. An API-key account's stored key goes with it.

Edit, Disable, Enable and Delete require the org admin role. Sign in, Add to node and Re-login need permission to add accounts. On the only enabled account, Disable warns Disabling this leaves no account eligible for new runner launches.

The Delete account dialog: the question naming the account and what goes with it, Cancel and Delete

Delete asks first, in Delete account: the question names the account and says what goes with it, the stored key for an API-key account, or the sign-in on every node and the shared folder for a subscription, with how many running sessions stop.

A node row has its own ⋯ menu:

  • Login, when the account isn't on that node, signs it in there.
  • Otherwise Deprovision removes the account's sign-in from that node, after you confirm with Remove in Remove credentials from node. The account's other nodes keep theirs; on the only node holding the account, its row leaves the list too. Requires the org admin role.

Share subscriptions between nodes​

Select Share to sign a subscription in once, on one node, and have every attached node reuse that sign-in. The button shows when your plan includes NodeLink and you may edit credentials. It opens the Share subscriptions between nodes page under NodeLinks; if your organization already shares subscriptions, it opens that NodeLink instead.

The Share subscriptions between nodes page: Name, Path, the Connection, the Storage choice New AWS EFS or Existing AWS EFS, the optional Allowed CIDR, the Nodes list with two nodes ticked, the confirmation, Cancel and Create

FieldMeaning
NameThe NodeLink's name. It starts as Subscriptions.
PathFixed: {jaah-home}/auth/.shared, the folder nodes read sign-ins from.
ConnectionThe cloud connection the storage is made or found in, shown when the storage is in your own cloud.
StorageWhere the shared folder lives: Jaah-managed, Storage in Jaah, New AWS EFS, Existing AWS EFS, New GCP Filestore, Existing GCP Filestore, New Azure Files (NFS) or Existing Azure Files (NFS), each with a line under it saying what it is and the fields described under NodeLink, such as Allowed CIDR. Only the chosen connection's cloud is offered. A new storage takes the NodeLink's Name.
NodesThe nodes the storage you picked can go on, all ticked; untick one to leave it out. A node it can't go on is greyed, with the reason beside it. The list is read again when you pick storage somewhere else.
ConfirmationI confirm my model provider allows one subscription on several devices. It must be ticked.

Create stays off until every field is filled, the nodes are read and the confirmation is ticked; the line beside it says which, such as Tick the confirmation to continue. Select Create to make the NodeLink, attach the ticked nodes, and open it. A notice there lists any node it was Not attached to, with the reason. Select Cancel to go back to the NodeLink list without creating anything; leaving with input asks first.

Add an account​

Select Add account. The New account form opens beside the list, with Add by set to Set up here; Import a file switches to importing an account. While your organization awaits approval, Add account is turned off and says why. The steps are in Add a model account.

The New account form for a subscription: Add by, Provider, Authentication, Name, the line naming providers off the plan, Node, Advanced, Cancel and Authenticate

FieldMeaning
ProviderThe agent this account runs. It can't be changed later. Only the providers your plan includes are offered.
AuthenticationAPI key or Subscription (OAuth), when the provider offers both.
NameStarts as the provider and authentication, such as Claude Code Subscription. Blank shows the slug, a short code Jaah picks.
Plan lineHow many providers your plan leaves out, for example 4 more providers are not on your plan. Hover the count for their names. Change plan opens your plan; a member without the org admin role reads Ask an admin to change the plan. See How model accounts work.
Project lineSubscription sign-in needs a project. Ask an admin to add you to one. A member on no project can add an API key, but has no node to sign a subscription in on.
API keyAPI key only. Stored, and never shown again.
Workspace IDClaude Code API key only, optional: the workspace for a key not scoped to one. It starts with wrkspc_.
NodeSubscription only: the node the sign-in runs on. Only nodes whose operating system runs the provider are offered. When a node reports the shared token folder mounted, it moves under Advanced and starts on that node.
AdvancedFolded; each field appears only when it applies.

When no node you can see runs the provider, a line under the form says why, with Add a Linux node, or use an API key. When there is nothing you may add, a warning reads No provider is on your plan. (with Change plan or Ask an admin to change the plan.), or You can’t add any allowed account. Ask an admin.

The New account form for an API key with Advanced open: Owner, Description and Auto-assign

Under Advanced:

FieldMeaning
OwnerPersonal or Organization. Requires the org admin role; a member's account is always their own.
DescriptionShown when you hover the account's name on AI Accounts.
Auto-assignOn: the account runs tasks that allow any provider. Off: only tasks that pick its provider.
Max runnersThe most runners at once. Blank: the organization's Concurrent runners for a subscription, no limit for an API key.

Add saves an API-key account. Authenticate starts a subscription's sign-in, which continues under the form:

ItemMeaning
Authenticate, Copy linkOpen the provider's page again. It opens in a new tab once the node has its link.
Authorization codeThe code the provider shows after you authorize. Confirm sends it, then reads Close.
Copy codeCopies a one-time code to enter where the link asks.
Waiting for you to authorize…Shown until you do. Back to accounts (keeps running) leaves it waiting.

When it's done, the page says Account added and enabled. and closes itself. Cancel closes the form without adding anything.

Import an account​

Select Import to add an account exported from another Jaah console. It shows when you may add accounts, and opens New account with Add by set to Import a file; Set up here switches back to the form.

New account with Add by set to Import a file: Choose file, Cancel and Import

FieldMeaning
Choose fileThe exported file. Once picked, it reads Change file, and the page names the account, its provider and API key or Subscription.
PassphraseAPI-key accounts only: the passphrase the file was exported with.

Import stays off until a file is picked and, for an API key, a passphrase is typed. Importing a subscription requires the org admin role. When it's done, the account opens: an API-key account arrives with Auto-assign off; a subscription has no sign-in yet, so its Log in page opens to sign it in on a node. Cancel returns to the list; leaving with a file picked asks first. See Move a model account between consoles.

An account's details​

Select an account's name, or Edit in its row menu. It opens in a pane beside the list, with the tabs Details and Access. Enabled at the right of the tabs switches the account on or off, and Export beside it saves the account to a file another console can import. Both require the org admin role.

Details​

The Details tab of an API-key account: the Enabled switch, Export, Name, Description, Owner, Slug, Provider, Authentication, API key, Workspace ID, Auto-assign, Created and updated by, Cancel and Save

Slug, Provider and Authentication are fixed, under Owner. You can change:

SettingMeaning
NameThe label the account shows everywhere. It can't be blank.
DescriptionA note shown when you hover the account's name on AI Accounts. Leave it blank for none.
OwnerPersonal, with the member in Owned by, or Organization. Requires the org admin role, on any account you can see. An API-key account's key follows the account.
API keyAPI-key accounts only. It shows Stored — leave blank to keep; type a new key to replace it.
Workspace IDClaude Code API-key accounts only. The workspace to name with a key not scoped to one; blank for a key that is.
Auto-assignOn: the account runs tasks that allow any provider. Off: only tasks that pick its provider.
Max runnersThe most runners at once. Blank: the organization's Concurrent runners for a subscription, no limit for an API key. Shown for every subscription and for some API-key providers.

Created by and Updated by name who made and last changed the account, when Jaah knows; one person doing both shows as Created and updated by. Select Save to keep your changes, or Cancel to go back to the list. If you can't change the account, the tab says Read-only — only an administrator can change an account.

Leaving the account with changes you haven't saved, with Cancel, a link, the sidebar or the browser's Back, opens Unsaved changes: This account has changes that have not been saved. Save them before leaving? Cancel keeps you on the account with your changes, Discard leaves without them, and Save saves them, then leaves; if saving fails, you stay.

Export​

The Export account dialog for an API-key account: the line The key is sealed with this passphrase. Import needs it., Passphrase with its 12+ characters hint, Confirm passphrase, Cancel and Export

For an API-key account, type a Passphrase of at least 12 characters and repeat it in Confirm passphrase; Export stays off until they match. For a subscription the dialog says The record only: the login stays on its nodes. Log in again after import. Select Export to download the file, or Cancel.

Access​

Who may use the account: people and groups. Managing the list requires the org admin role, on a personal account too.

The Access tab: a Filter box, Add, and the Member, Last active and Source columns, each row with a ⋯ menu

  • Filter narrows the list.
  • Each row is a person or a group. A group shows how many members it has; select + to list them.
  • Member is the person or group.
  • Last active is when they were last active. In a narrow pane it folds into one line under the name, such as Active 36s ago.
  • Source says how they hold it: Direct, Via a group, or From the organization. A member who holds it through a group of the organization reads Via the group · from the organization.
  • A row's ⋯ menu offers Remove for someone added here. For access held through the organization or a group it offers Open group to remove (or Open org to remove) instead, which opens it there: it is removed there, not on this account.

To give someone access, select Add, pick people or groups in Who, and select Add.

Tasks run on an organization account when the person who started them is on its list, or holds Project Developer or higher on the task's project, or is an Org Owner or Org Admin. A personal account runs its owner's tasks and those of the people and groups on its list.

Sign an account in again​

Re-login in a row menu, or Login on a node row, opens the sign-in for a subscription whose sign-in expired or was refused. It needs permission to add accounts; an API-key account has nothing to sign in. The steps are in Sign a model account in again.

Re-login for a subscription: Slug, Provider and Authentication fixed, the Node picker, Cancel and Authenticate

The page is titled Re-login and the account's name. From Add to node it reads Add name to a node, and from a node row's Login, Add name on node. Slug, Provider and Authentication are shown fixed.

Add to node for a subscription: the title Add claude1 to a node, Slug, Provider and Authentication fixed, the Node picker, Cancel and Authenticate

FieldMeaning
NodeThe node the sign-in runs on, or Chosen automatically. From Add to node, only the nodes the account isn't on yet are listed. From a node row's Login, that node, fixed. A sign-in belongs to its node and doesn't move to another.
AuthenticateStarts the sign-in, which continues as when adding an account.

Cancel goes back without signing in. Instead of the form, the page says Nothing to sign in for an API-key account, No node to add it to when the account is already on every node, and Not allowed without permission to add accounts.

When it's done, the page says Re-login complete — credentials refreshed., or Signed in on this node. from a node row.

See Secrets for connections to other services, and Nodes for the machines runners work on.