Availability and Limitations

Organizations currently supports:

• Multiple accounts per Organization, with segregated balances, orders, and history
• Full account lifecycle: add, edit, disable, enable, and delete accounts
• Team access through Account Roles and Workflow Profiles, with system-defined options ready at creation
• Seven governed workflows with per-workflow approval policies and policy locking
• Transfers between accounts and withdrawals to whitelisted addresses, both under full governance
• Spot trading on every account; margin trading on the main account
• Earn allocation and deallocation
• API keys mapped to one or more accounts, with governed key administration and FIX connectivity for spot trading
• Security events covering sign-ins, fund movements, and every administrative change
• Organization Sign-in 2FA and session timeout policies

Margin trading is main-account only

Members with the Trade permission can trade spot and margin on the main account, and spot on additional accounts. Margin support for additional accounts is planned, when it arrives, per-account margin will follow the same permission model as every other account permission.

What this means day to day: run margin strategies from the main account and spot activity from the others. The same Trade permission behaves differently on the main account versus the others, so label your accounts clearly for your team.

Owner-only operations

Some platform operations have no Organization permission yet and remain exclusive to the Organization Owner, operating on the main account:

• Futures trading
• TradFi Futures trading
• Equities trading
• xStocks trading
• Options trading
• OTC trading
• Convert
• DeFi Earn
• Loans

WebSocket trading on accounts other than the main account is also Owner-only.

The Owner performs these through the same flows as before the Organization was created. Members cannot access them regardless of their roles and profiles.

Up to 100 accounts per Organization

An Organization currently supports up to 100 accounts, including the main account. If your operation needs more, contact Support to discuss raising the limit.

One Workflow Profile per Member

Each Member holds exactly one Workflow Profile. Teams needing a combination of levels that no existing profile provides create a custom profile rather than stacking profiles. Account Roles, by contrast, stack freely.

Members belong to one Organization

Each Member currently belongs to a single Organization.

Organization exit requires support

Organizations does not provide a self-service delete or revert action. Support can move a user out of Organizations after the required conditions are satisfied. The user record remains subject to the applicable data-privacy rules.

Organization Owner email changes do not transfer ownership

The Organization Owner’s email address can be changed through the regular Email Change flow. Expect ID verification and possibly a manual review as part of that process. Changing a Member’s access does not transfer ownership from one Member to another.

Approval rules do not vary by account

Policies are set per workflow for the whole Organization. Approval rights (the Approve level) apply Organization-wide, a Member who can approve withdrawal requests can approve them from any account. Configurations like “approve only for certain accounts” or “require extra approvals on one specific account” cannot be expressed today. Control who approves by narrowing who holds Approve; control where funds move by narrowing fund-movement permissions.

API keys apply permissions uniformly

An API key’s permissions apply to all of its selected accounts equally, there is no per-account variation within one key. Use multiple narrowly scoped keys where automation needs different access on different accounts. See API keys.

Funds are not reserved while a request awaits approval

A pending withdrawal or transfer request does not set the amount aside. The balance check runs when the request completes, after the final approval, so if the funds moved during review, the approved request fails and must be resubmitted. Nothing is lost when this happens; it is simply a resubmission.

Reserving funds at request creation is planned. Until then, treat submitted requests as spoken-for balance. See Keep the funds available until approval.

Account deletion archives records

Deleting an account archives its record and hides the account from end-user operating surfaces. The account must be empty and settled first, and the system never auto-cancels orders, auto-moves funds, or auto-unwinds products to get there. Deletion blockers are listed explicitly and resolved manually. See Accounts.

No public Organizations management API

Member invitations, access assignment, account lifecycle, and policy configuration are available in the UI only. Programmatic access is limited to API keys operating on their supported flows: trading, Earn, queries, data exports, and starting withdrawal and address requests. Check the Kraken API documentation for current API coverage.

Areas under active development:

• Margin trading on additional accounts, with a dedicated per-account permission
• Per-account credit lines
• Reserved funds for pending requests, submitting a withdrawal or transfer request will set the amount aside, so approved requests never fail because the balance moved during review
• Account groups, named, reusable sets of accounts for scoping roles at scale
• Expanded permission coverage for more platform operations
• Organizations management API for programmatic administration

Timelines and availability are communicated through official Kraken channels.