The documented entities

Kalshi sub-users have their own login and permissions for reading, trading and transfers within an account. A subaccount holds a separate balance and positions. Sub-user permissions cover the account's subaccounts. To confine API trading to one subaccount, the documentation describes a restricted API key. Availability depends on account eligibility. Kalshi · Sub-users vs Subaccounts ↗

An expectation that needs testing

Imagine two strategies with separate balances and a new team trader. A strategy label alone leaves the access configuration to verify. Determine which login or key performs an operation, its permissions and the balance selected in the request. Check transfer access separately and expose the relevant settings before submission.

Testing the team configuration

Exercise both an intended permitted action and an action beyond the expected boundary, retaining results with the settings. Also establish whether server records identify the individual actor. Where account-level records do not, a panel's own audit log can link staff, requests and results for later reconciliation and handover.