Billing & Subscription

#Overview

Your organization is a single tenant on Opal — the top-level container that holds its members, teams, roles, resources, and organization-wide settings. It is also where the company's commercial relationship with Opal lives: how it is billed, what it is subscribed to, and how many seats it holds.

Billing & Subscription covers four things:

• The billing profile — the organization's billing details.
• Payment methods — how the organization pays.
• The subscription plan — what the organization is subscribed to.
• Seats — the places on that subscription.

All four are managed in Organization Settings — the central area where an organization's profile and preferences, security, membership, teams and roles, billing, and credits are administered. Billing is not off in a separate system; it sits next to the rest of organization administration.

This matters for two reasons, and only one of them is financial. The first is keeping the organization funded and in good standing, so work is never interrupted for a reason as avoidable as a lapsed payment method. The second is capability: the plan is one of the gates that determines what the organization can use. Some features are available only on particular plans, which makes the plan a product decision as much as a commercial one — and it is often the answer when a team lead asks why a setting is not available to them.

One boundary is worth setting up front. This page covers the subscription and how the organization pays for it. The credit balance that funds day-to-day usage — top-ups, recurring credit subscriptions, automatic top-ups, and billing alerts — is a separate topic, covered by Credits.

#Key Capabilities

• Maintain the billing profile. The organization's billing details are held in one profile, managed at organization level rather than per member.
• Manage payment methods. The organization's payment methods are managed alongside the billing profile, so how it pays stays current.
• Manage the subscription plan. The plan the organization is subscribed to is managed here.
• Manage seats. The seats the organization holds on its subscription are managed as part of billing, not as part of membership administration.
• Understand what the plan unlocks. Some capabilities depend on the plan — for example, SAML single sign-on is available on the Enterprise plan only, and sharing a resource with members or teams at a given permission level is available on the Business and Enterprise plans.
• Administer it alongside everything else. Billing sits in Organization Settings with the organization's profile and preferences, security, membership, teams and roles, and credits, so there is one place to go for organization administration.

#How it Works

Everything is managed from Organization Settings. An organization's settings are managed from a central Organization Settings area, where administrators control everything from the profile and preferences through to security, membership, billing, and credits. Billing is one section of that area.

The billing profile and payment methods describe how the organization pays. The billing profile holds the organization's billing details, and its payment methods record how payment is taken. Both belong to the organization as a whole, which is why they are kept in Organization Settings rather than in any individual member's own settings — a change of finance contact or card is made once, for the whole organization.

The subscription plan is what the organization is subscribed to. The plan is managed in the same place as the billing profile, payment methods, and seats. Changing plan is therefore a billing action, taken by whoever holds the organization-level permissions for it.

Seats belong to the subscription, not to membership. Deciding who is admitted to the organization — invitations, verified email domains, and approving join requests — is membership administration, covered by Members. The seats the organization holds are part of its subscription and are managed with the rest of billing. In practice the two are read together: membership tells you who is in, and the subscription tells you what the organization is paying for.

The plan is one of three gates on what the organization can use. Whether an action is available depends on the organization's plan, the role permissions granted to the person attempting it, and, for an individual resource, the permissions set on that resource. The plan is the gate this page is responsible for, and two documented examples show how it behaves: SAML single sign-on is an Enterprise-plan security setting, and resource-level sharing with permission levels is available on the Business and Enterprise plans. The full model — all three gates and how they interact — is documented once, in Access & Permissions.

The subscription and credits do different jobs. The subscription is the commercial relationship: what the organization is subscribed to, how many seats it holds, and which capabilities that unlocks. Credits are the balance the organization uses to fund its usage of Opal. The two are complementary rather than interchangeable, and both are administered in Organization Settings. Credits are covered by Credits.

#Additional Notes

• Plan names appear only where a capability depends on them. Where this documentation names a plan — Business or Enterprise, for example — it is because a specific capability depends on that plan. Those mentions are not a complete list of the plans available, and this documentation does not publish prices or tiers.
• Figures and mechanics are not documented here. Prices, billing cycles, seat limits, and the payment-method types accepted are not covered in this documentation. Check the billing section of Organization Settings for what applies to your organization.
• Credits are covered separately. The credit balance, one-time top-ups, recurring credit subscriptions, automatic top-ups, and billing alerts all belong to Credits.
• Marketplace payouts are not billing. Money the organization receives for selling its own resources is handled separately from what it pays for its subscription: Payouts.
• Some security settings depend on the plan. SAML single sign-on is available on the Enterprise plan only. Enforced multi-factor authentication is an organization-wide setting an administrator can apply to all members. Both are covered by Security.
• Short definitions of the terms used here are in one place: Glossary.

#Related Features

• Billing & Credits — The cluster this page belongs to: the subscription, how the organization pays, and the credits that fund its usage. Billing & Credits
• Credits — How credits work and how to keep the balance topped up, including recurring credit subscriptions, automatic top-ups, and billing alerts. Credits
• Members — How people join the organization, by invitation or through a verified email domain, and how join requests are approved. Members
• Security — The organization's security settings, including enforced multi-factor authentication and Enterprise-plan SAML single sign-on. Security
• Organization — The starting point for organization-level administration, where each settings area is introduced. Organization
• Access & Permissions — The full access model behind plans, role permissions, and per-resource permissions. Access & Permissions
• Glossary — Short definitions of the billing and subscription terms used on this page. Glossary