Create an Organization

Last updated: August 17, 2026

Before you create an Organization, confirm the following:

  • You have a Business verified Kraken account on Kraken Pro. Standard and Starter accounts are not eligible, and business verification must be complete before creation.
  • You are the account holder, the person who completed the business verification (KYB).
  • You have reviewed the current limitations of operating within an Organization. Some features may not be available.
Caution:

Before you start adding new Members, sketch your team on paper: who trades, who moves funds, who approves, and who administers. The system-defined roles and profiles cover the common patterns. Having a clear picture of who does what in your team will simplify the initial setup.

  1. Sign in to your Kraken Pro account.
  2. Go to Settings > Organizations.
  3. Select Create Organization.
  4. Set the Organization name that your team will see when they sign in.
  5. Choose the Organization Sign-in 2FA policy for all Members, either Passkey only or Authenticator app or Passkey. This policy applies to every current and future Member. Members who do not meet the requirement are blocked from accessing the Organization until they comply.
  6. Review the configuration summary.
  7. Select Confirm to create your Organization.

Organization Sign-in 2FA policy

All Organizations require two-factor authentication. During creation you choose the Organization Sign-in 2FA level that applies to every current and future Member.

2FA level

What it requires

Passkey only

Members must register and authenticate with a passkey (hardware security key or platform authenticator).

Authenticator app or Passkey

Members must have at least one of an authenticator app or a passkey enabled on their account. Either method satisfies the requirement.

Important:

The Owner can change the Organization Sign-in 2FA level after creation but cannot disable 2FA entirely. At least one of the levels above must always be active.

Session timeout

A configurable idle session timeout applies to all Members. When a Member’s session is idle for longer than the timeout period, the session is terminated and the Member must sign in again.

Session timeout is configured from the Organization security settings after creation. Shorter timeouts reduce the risk of unattended sessions being misused.

After you create your Organization:

  • You become the Organization Owner, holding the system-defined Admin profile and Full access role, full ability on every workflow and every account.
  • Your existing account becomes the Organization’s main account. All balances, positions, and settings remain unchanged.
  • No other Members exist yet. You operate as a single-user Organization until you invite your team.
  • Every workflow’s policy starts open: requests from Members with Execute complete immediately. You can tighten policies after you have invited more Members. See Rolling out governance.
  1. Open your accounts - Go to Accounts and create the operating units your teams need, one per desk, strategy, or function. See Accounts.
  2. Invite your first Member - Go to Team, invite a Member, and assign them a Workflow Profile and one or more Account Roles. The system-defined options cover the common cases. See Roles, profiles, and permissions.
  3. Configure your first policy - Set approval requirements for your high-risk workflows. Most Organizations start with Withdrawal Request or Transfer Request. See Policies, approvals, and governance.
  4. Test the approval flow - Submit a test request and verify that the right Members can approve it.
  5. Lock when ready - Once you are confident the approval flow works, lock the policy to prevent unilateral changes. See Rolling out governance.
Note:

You can introduce approvals one workflow at a time, at your own pace. Nothing forces full governance on day one.

Need more help?