> 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/platform-guide/settings/organizations-and-billing.md). # Organizations and billing Create an organization to get a shared cloud workspace: a shared account list, member addresses, members and roles, and billing. **Where:** **Account** menu → **Create organization**, then **Settings → Organization** · **You need:** sign in, and a completed checkout ## Before you start: sign-in and the waitlist Sign in if you have early access. Otherwise join the waitlist from the same dialog. Sign-in works today, for early-access accounts. You do not need any of this to use the Platform. The **Free** path is open to everyone, needs no account, and enforces exactly the same on-chain policy. Signing in adds an identity (profile, privacy, organization invites) but no hosted service. An organization adds a shared workspace and hosted services such as watched addresses and alerts, and it is paid. ## What an organization is The Create organization page reads "Organizations hold shared member addresses, members, and the paid plan." An organization is a **space**, separate from your **Personal** space. Its account list has **Cloud** residency: it is stored by Bloxchain and shared with every member. Your Personal list stays on this device. Plans: **Free** and **Account** (optional sign-in) are individual paths. **Pro** and **Team** are self-serve organization plans. **Enterprise** is contact us. There is no Personal plan. Pricing is shown at checkout, or on request for Enterprise. ## What an organization buys Organizations exist today and every one of them is paid. What you get is collaboration and shared governance around the account, never a change to who may act on-chain. | What you get | What it means day to day | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Shared account list (**Cloud** residency) | A new team member signs in and sees the team's accounts, instead of importing each one by address | | **Member addresses** | One shared address book, "used for access control and audit", so a signer, requester or approver shows up with a name instead of a raw address | | Members and organization roles | Decide who may administer the organization and its billing, separately from the on-chain roles on any account | | Organization networks | Everyone reads the same chain through the same RPC | | **Billing** and **Invoices** | One payer, one place for receipts | What an organization does not change: * The on-chain policy is the same on every plan. Roles, permissions, gates, allowlists and the time lock are enforced by the contract, not by your subscription. * Bloxchain never holds a key. Every member signs with their own wallet. * Organization membership grants nothing on-chain. Only a role on the account does, and that is assigned under **On-chain access**. For the governance model these features support, who holds **Owner**, **Broadcaster** and **Recovery**, how to onboard and offboard a member, and what the audit trail proves, read [Organization governance](/guides/organization-governance.md). ## Create an organization 1. Sign in, open the **Account** menu and click **Create organization**. 2. Pick a plan. 3. The organization is created and you are taken to checkout. 4. Complete checkout. The organization shows "Organization active". Until checkout completes the organization is in the **Checkout required** state. Residency reads **Cloud off** in the **Account** menu and in Settings, the Accounts page says "No accounts available. This organization is inactive until billing is settled.", and shared features stay locked behind "This organization is inactive. Activate a paid plan in Billing…" covers. An inactive organization is never the same as the Free path. ## Billing & Plans **Settings → Organization → Billing** has two tabs. | Tab | Contents | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Plans** | The current plan and upgrade options, with pricing shown at checkout. "Paid plans are billed to an organization." The **Organization workspace** section explains: "Shared member addresses, assignment, and role-based access unlock on Pro." | | **Invoices** | Table with Date · Description · Amount · Status · Receipt. | ## Member addresses The page reads "Member addresses shared with this organization — used for access control and audit. Non-custodial: Bloxchain never holds a key." Member addresses are the organization's address book. Adding an address here does not grant any on-chain role; it lets the organization recognise the address when it appears as a signer, requester or approver, and label it in audit views. 1. Click **Add address**. 2. Enter the **Wallet address**, an optional **Label**, and pick an accent colour. 3. Save. ## General and Members & Roles * **General**: organization name and basic settings. * **Members & Roles**: invite people by email, assign organization roles (who may administer the organization and its billing). These are hosted roles for the organization, not the on-chain roles of any smart account. ## Organization networks An organization can save networks that every member sees, separate from the device networks in [Settings → Networks](/platform-guide/settings/networks.md). Add them from the organization's settings so the whole team reads the same chain through the same RPC. ## Switching spaces Open the **Account** menu. Under **Workspaces** you see your Personal space and each organization. Pick one to switch. The **This device** badge disappears from the top bar: it is shown only for a local list, not relabelled. Residency then reads **Cloud** (or **Cloud off**) in the **Account** menu and in Settings, and Accounts shows that organization's list. ## What Cloud residency means | | This device | Cloud | | ------------ | ------------------------------- | ----------------------------------------- | | Account list | Your browser | Bloxchain hosted, shared with members | | Backup | Export JSON | Managed by the organization | | Keys | Your wallet | Your wallet. Bloxchain never holds a key. | | Who can open | Anyone with the link, read-only | Members who sign in | Residency is about the list and the labels. Every signature and every rule stays on-chain and in your wallet, regardless of plan. ## Related * [Settings](/platform-guide/settings.md) * [Profile, notifications and privacy](/platform-guide/settings/profile-notifications-privacy.md) * [Free, sign-in and organizations](/introduction/free-sign-in-organizations.md) * [Roles and permissions guide](/guides/roles-and-permissions.md) --- # 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/platform-guide/settings/organizations-and-billing.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.