> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/staking/stake-cosmos/enable-atom-staking.md).

# Enable ATOM Staking

{% hint style="success" %}
This section is for Administrators only.
{% endhint %}

## Enabling Cosmos staking on an account

You can enable staking for any Cosmos account. The *Step 4 staking rule* of the Create an account or edition procedure lets you activate and configure a rule to govern staking transactions. The staking rule governs all Cosmos staking transactions: delegating ATOM to a validator, claiming rewards, undelegating your assets and redelegating assets to a validator. Activate the feature by clicking on the **Toggle** button, and configure your **Staking governance rule** according to your needs.

1. Select creator to define which operators can create staking transactions. You can select up to 20 operators or a single group.
2. Use the approval workflow section to define which Operators must review and approve staking transactions created in the account. You can define up to three steps.
   1. Click Add approval step .
   2. Select up to 20 Operators or a single group.\
      *Operators and groups pending to be created, edited, or deleted won't be listed.*
   3. Click the chevrons   to define the number of approvals required from these Operators.
   4. Click Add approval step .


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.enterprise.ledger.com/staking/stake-cosmos/enable-atom-staking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.