Skip to main content
Once you have an active subscription, you can manage it from Admin Panel > Plans & Billing. The billing page shows your plan, next payment date, and current seat usage.

Managing Seats

Every active user in your workspace counts as a seat, including Slack bot accounts. You can adjust your seat count at any time.
1

Open seat management

Click Update Seats on the billing page.
2

Set the new count

Enter your desired number of seats. You cannot go below the number of seats currently in use (active users + pending invitations).
Need to reduce seats below current usage? Remove users first, then adjust the seat count.
3

Review the billing impact

  • Adding seats — you’ll be billed a pro-rated amount immediately.
  • Removing seats — the change takes effect at the end of your current billing cycle.
4

Confirm

Click Confirm Change to apply.

Stripe Customer Portal

Click Manage Plan on the billing page to open the Stripe customer portal. From there you can:
  • Update your payment method
  • View and download invoices
  • Cancel or modify your subscription

Air-Gapped License Activation

For self-hosted deployments without internet access, you can activate a license manually instead of going through Stripe checkout. Contact the Onyx team at support@onyx.app to request a license file. You will receive a file containing your signed license in this format:
1

Open Plans & Billing

Navigate to Admin Panel > Plans & Billing from the sidebar.
2

Open the license form

Click Activate License Key at the bottom of the billing page.
3

Upload your license

Paste the contents of your license file, or use the file upload button to attach it directly.
4

Activate

Click Activate License. Your license will be validated and paid features will be enabled immediately.
To update an existing license (e.g., after renewal or a seat change), click Update License Key instead and follow the same steps.

Downgrade to Community Edition

A self-hosted deployment whose license has lapsed can drop to the free Community Edition instead of renewing. The option appears only while the workspace is locked (the Access Restricted page), as a Downgrade to Community link at the bottom of the billing page and as a button on the lock page itself. Only admins see it.
The downgrade cannot be undone. Content that was restricted by synced permissions or user groups becomes visible to every user of the workspace.
Confirming the consent dialog does the following in one step:
  • Every connector becomes public. Permissions synced from the source (Google Drive, Confluence, SharePoint and so on) stop applying, and connectors restricted to user groups open up. Search results follow once the document index has been rewritten, which can take a while on a large index.
  • User groups are removed. Agents, document sets, LLM providers, MCP servers and skills that were shared with a group become public. Published agents are view-only for everyone except their owner. Members of a group that granted admin rights keep them through the default Admin group.
  • Paid features are switched off. Service account API keys, token rate limits and hooks are deleted. Standard answers and SCIM tokens are deactivated. Custom branding and chat retention are reset.
  • The license is removed from the deployment.
No indexed data is deleted, and chats, agents, connectors and users stay as they are. If the request fails part way, nothing is lost: the license is removed last, so the deployment stays licensed and running the downgrade again finishes the job. To return to a paid plan later, subscribe or upload a license file again. Connector permissions and user groups are not restored by that. Set them up again after the license is active.