> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/guides/guides.md). # Guides overview End-to-end recipes that take a freshly deployed smart account to a working, tested setup on Sepolia. **Where:** Discover, then inside the account (Policies and On-chain access) · **You need:** a wallet on Sepolia with test ETH, plus one or two extra test wallets ## How the guides work If you have not deployed an account yet, the [Quickstart](/get-started/quickstart.md) does that part, and [How it works](/introduction/how-it-works.md) explains the request lifecycle every guide exercises. Every guide starts from the same place. You choose a preset on **Discover** and deploy a governed account. Today every preset deploys the same account, and it lands as a **Vault**: a finished, locked account that holds assets but has no spending capability yet ([what that means](/platform-guide/policies/actions.md#what-a-new-account-already-has)). The guides then walk you through what the owner configures afterwards: 1. **Security** ([Policies](/platform-guide/policies.md)): owner, recovery, time lock and broadcasters. 2. **Actions** (Policies): the functions the account may perform. 3. **Roles** and **Signers** ([On-chain access](/platform-guide/access.md)): who holds which duty. 4. **Manage permissions**: which role may perform each step of each action. 5. **Gates**: the on-chain grants that let a role's action run. 6. **Allowlists**: where value or calls may go. 7. A test with a member wallet, so you see the flow before real funds are involved. ## Pick a guide | Guide | Who is involved | Time | Outcome | | ------------------------------------------------------------------- | ------------------------------------- | -------- | --------------------------------------------------------------------------------------- | | [Personal security account](/guides/personal-security.md) | One person, two wallets | \~30 min | A time-locked account where a transfer you did not mean can be cancelled while it waits | | [Team treasury](/guides/team-treasury.md) | Requester, approver, broadcaster | \~45 min | Payouts that need one wallet to request and another to approve | | [Asset issuance](/guides/asset-issuance.md) | Minter requester, compliance approver | \~60 min | Mint and burn of your own ERC-20 only after review | | [Allowlisted contract calls](/guides/contract-calls.md) | Integration signer, broadcaster | \~60 min | Governed calls to approved external contracts, restricted by the contract allowlist | | [Approve from another device](/guides/cross-device-approval.md) | Requester, approver, broadcaster | \~15 min | An approval signed on one device and submitted from another with a signed file | | [Designing roles and permissions](/guides/roles-and-permissions.md) | Owner or admin | Reading | A role model that stays safe as the team grows | | [Organization governance](/guides/organization-governance.md) | A whole team | Reading | Duty separation, onboarding and offboarding people, and a review routine | | [Approve with an agent's help](/guides/agent-assisted-requests.md) | An agent plus a person | \~20 min | An agent drafts and signs a request, a person reviews and broadcasts it | | [Ways to configure an account](/guides/ways-to-configure.md) | Owner or developer | Reading | The five routes to a configured account, and when each one fits | ## How the guides relate to the Platform pages The [Platform](/platform-guide/platform.md) section documents one screen per page: what each field means and what happens when you press a button. The guides string those screens together into a task. When a step needs more detail, follow the link to the Platform page and come back. Start with [Designing roles and permissions](/guides/roles-and-permissions.md) if you are setting up an account for a team, then [Organization governance](/guides/organization-governance.md) for how a group of real people runs it together. If you would rather script the setup than click it, [Ways to configure an account](/guides/ways-to-configure.md) lays out every route. Before any real value moves, work through [Security best practices](/security/security-best-practices.md). {% hint style="warning" %} Alpha · Local-first. All guides run on Sepolia with test ETH. Official deployments are live on the 15 supported networks, in the Platform and in the Protocol. {% endhint %} --- # 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://docs.bloxchain.app/guides/guides.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.