> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kuru.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Trading Permissions

> Give a bot access and understand the scope of that access.

You can authorize another wallet to act for your Kuru account. This is useful for a trading bot or an application that signs actions on your behalf, without sharing your owner key.

## Access covers the whole account family

Permissions apply to your main account and every current or future subaccount. You cannot give a signer access to just one subaccount in this account model.

| Permission | What it allows |
| - | - |
| Trading | Place, replace and cancel orders; swap; manage passive liquidity; create subaccounts; configure permitted trading hooks |
| Internal transfers | Move available funds between accounts owned by the same root |
| Withdrawals | Withdraw from the main account to a chosen recipient, and transfer funds within the family |
| Administration | Manage signers and exercise all of the permissions above |

Trading access can change the value and composition of your holdings. It is not a spending limit or a restriction to particular markets. Use separate owners when strategies require separate permission boundaries.

## Expiry and revocation

Access may expire at a chosen time or remain active until revoked. Permissions are checked when an action executes, not only when it is signed.

Revoking a signer removes its access across the family. It does not cancel resting orders or remove passive liquidity. Decide separately whether to close those positions.

Granting or revoking a signer also invalidates older signed trading instructions that use the previous authorization state. Other bots using the same owner may need to refresh their instructions. Creating a subaccount does not cause this invalidation.

## Rotating a key

Stop new instructions from the old signer, reconcile outstanding transactions, and revoke its permissions. Grant the replacement the permissions it needs, confirm the authorization, and resume using fresh instructions.

Logging out of Relay or letting its login token expire does not revoke onchain permissions. Developers should follow [Signer Lifecycle and Nonces](/sdk/signer-lifecycle).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.