> For the complete documentation index, see [llms.txt](https://docs.sqrl.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sqrl.tech/readme.md). # Introduction SQRL gives authorised users a controlled way to issue, manage, and move SCL tokens within an institutional workflow. These operations are anchored to Bitcoin. Each value-moving action requires cryptographic signatures from authorised signers. SQRL coordinates this process. It collects signatures, enforces policies, and broadcasts finalised transactions. Your private keys remain under your control at all times. This documentation covers the complete operator workflow: initial login, workspace setup, vault creation, token deployment, movements, and ongoing monitoring. It is written for institutional operators, workspace administrators, signers, and compliance staff. You do not need prior knowledge of Bitcoin or blockchain technology to use it. ## What you can do in SQRL You create organisational vaults, deploy tokens, move value across your organisation, and enforce governance controls. You assign roles and permissions to control who can initiate, sign, and monitor operations within each workspace. Every operation that moves value on the Bitcoin network requires cryptographic signatures from authorised signers. SQRL collects those signatures, enforces vault policies and movement limits, and broadcasts finalised transactions. SQRL stores only public key identifiers and never has access to your private keys. ## How the control model works SQRL is built for institutional use. It assumes multiple users with different roles, signing thresholds for sensitive operations, and a full audit trail. Each workspace is an isolated environment with its own users, roles, vaults, and policies. Every vault is configured with a signing threshold, for example 2-of-3. No value can move until the required number of authorised signers have provided their signatures. Policies restrict movements further by enforcing amount limits and cycle-based reset periods. The audit log records every significant action for compliance review. {% hint style="info" %} SQRL is non-custodial. It never holds, accesses, or controls your private keys or funds. Every value-moving operation requires cryptographic signatures produced outside the platform. SQRL stores only public keys. If you lose access to your private key, neither Orobit nor SQRL can recover it. {% endhint %} ## Who this documentation is for * **Workspace administrators** who set up workspaces, manage users, and configure policies. * **Signers and approvers** who review and sign pending movements and token deployments. * **Initiators** who create movement requests for others to sign. * **Auditors and compliance staff** who monitor activity logs and review controls. Where a technical concept is relevant to your work, it is explained in plain terms. For protocol-level detail on SCL and Bitcoin anchoring, see [docs.orobit.ai](https://docs.orobit.ai). ## How this documentation is organised The documentation follows the order in which you set up and operate the platform. * **Getting Started** covers your first login, two-factor authentication, and navigation. * **Organisations and Workspaces** covers the structural foundation of the platform. * **Users, Roles, and Permissions** covers access control. * **Signing Profile** covers your personal key management. * **Vaults**, **Whitelist Management**, **SCL Tokens**, and **Movements** cover day-to-day operations. * **Monitoring and Audit** covers notifications and the audit log. * **Appendices** include a glossary, a complete permission reference, a status reference, and troubleshooting. If you are setting up SQRL for the first time, read the sections in order through Vaults. If you are joining an existing workspace, start with Getting Started and Signing Profile, then read the sections relevant to your role. ## Key concepts You will meet these terms throughout the documentation. Each is defined in full in the [Glossary](/appendices/glossary.md). * **Organisation** — the top-level entity that contains all your workspaces, users, and resources. * **Workspace** — an isolated operating environment within your organisation. * **Vault** — an organisational construct that holds assets and enforces multi-party signing. * **Signing Profile** — your personal interface for managing the public keys you sign with. * **Key** — a public key identifier registered with SQRL. Private keys are never stored. * **SCL (Simple Contract Language)** — Orobit's contract language for tokens on Bitcoin. * **Token** — a digital asset deployed on Bitcoin using SCL, owned by a vault. * **Threshold** — the minimum number of signatures required to authorise an operation. * **Movement** — any value-moving operation: Mint / Issue, Burn / Redeem, or Transfer. * **Whitelist** — a set of approved addresses a token contract can interact with. * **Policy** — rules that govern movement limits and cycle periods. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sqrl.tech/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.