> 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/fundamentals/getting-set-up/for-operators.md). # For Operators {% hint style="success" %} **This page is only for Ledger Enterprise users that have Operator access. Please navigate to the** [**For Administrators**](/fundamentals/getting-set-up/for-administrators.md) **page if you are an Operator.** {% endhint %} An Ledger Enterprise operator is responsible for completing actions on the system. They handle tasks such as creating and approving transactions. See below how to begin configuring your workspace. #### Step 1: Accounts * Get started by going to the Accounts page to find out which accounts you've been granted access to. * Open each account and go to the *Rules* tab to find out if you can create and/or approve transactions in the account. Note that if you belong to a group, only the group name is displayed. #### Step 2: Generate a receiving address If your accounts are empty, click Receive in the left panel to Generate a receiving address for each of them and transfer funds. #### Step 3: Create your first transaction request * You can create transaction requests in accounts in which you have been added to the transaction creator step of the transaction rules. * Depending on how the account has been configured by Administrators, you might encounter restrictions to the amount you can send and/or receive. * To find out how transaction rules are configured in an account, go to Accounts > Account dashboard > Rules tab. * Finally, once the request is created, it must be approved by Operators selected in the approval workflow of this rule. #### Step 4: Keep track of transaction requests Once you've created a transaction request, you can follow its status from the Operations page. --- # 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/fundamentals/getting-set-up/for-operators.md?ask=&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.