Plans and subscriptions displays effective commercial choices for the active tenant. Availability depends on tenant type, lifecycle, plan and authorized offers. A displayed price, a checkout order and an active subscription are different stages. Always read current amounts, currency, period and conditions in the platform; this manual does not establish prices.
Before you begin
Confirm tenant and role before opening checkout. Learn in a separately authorized payment test environment. A public trial should continue as the same operational tenant after accepted conversion; do not recreate the workspace to simulate conversion.
Procedure
- Open Plans and subscriptions and inspect plan, lifecycle and capabilities available to your role.
- Read the displayed offer version, price, currency, period, quantity, taxes and terms. Tenant-specific offers reference the versioned global catalog.
- When evaluating an authorized purchase, review customer details, document, legal name, email, country, address and payment method before proceeding.
- For an exercise, use only fixtures or an independently authorized sandbox. Never submit synthetic tokens to a live provider.
- After an authorized purchase, inspect the definitive order and subscription outcome. Investigate the existing order before repeating checkout.
- Confirm that tenant identity and Repository object identifiers remain unchanged and that capabilities match the accepted subscription.
- For renewal or changes, inspect validity and contractual version again. A new price does not rewrite historical orders.
Verify the result
Conversion has an accepted commercial outcome, retains the operational tenant and grants matching capabilities. DovaAI allowances and user/capacity limits depend on the effective contract; do not infer unlimited access from an administrative title.
Errors and recovery
If an offer is missing, check eligibility, lifecycle, role and plan. If amounts disagree, confirm currency and quantity before submitting. A pending outcome requires resolving the earlier order rather than creating another as a test. Do not mark an invoice paid merely to enable features.
Synthetic example
In an authorized sandbox, review the Training offer, cancel before payment when only learning the form and verify that no unintended subscription was created.
Verification scope
Use synthetic data and the role authorized for the task. Compare a visual confirmation with the saved record or relevant attempt. Retain only safe identifiers and messages for support; do not share secrets, personal information or tenant data. If an operation outcome is uncertain, check its state before repeating it.
Environment context
Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.
Environment worker pool
In Configuration → Dova Integration Runtime, Environment worker pool identifies the current environment. Allowed workers assigns existing workers; Default worker must belong to that selection. Pool policy starts as Dedicated. Select Shared only when you explicitly want to share capacity and every participating pool also declares Shared. A matching name does not share a physical worker.
Save environment pool changes only the selected environment’s policy and neither starts a job nor changes the tenant’s global default. The review uses a configuration fingerprint; if another user changes it, Refresh pool lets you reload and review before saving. Controls require configuration and environment Runtime administration. Built-in is not offered as an execution worker.
Production does not automatically borrow the Development pool. New jobs require an explicit pool, apart from the public Development option for an eligible Trial described below. Legacy execution can retain an earlier worker only when the server verifies the exact published chain, configuration and permitted membership. Test and Stage consume the plan’s Development bucket; Production uses the Production bucket. Pool membership does not replace capacity, online status, profile compatibility, quotas or concurrency.
Public Trial: platform-managed Development pool
An eligible public Trial can automatically use the platform-managed public Development pool when no explicit Development policy exists. An explicit policy, including an empty one, takes precedence. This grants neither private workers nor permission to save pools; availability and plan limits still apply. See workers and capacity.
Subscription recovery
The funding projection uses Billing’s canonical period representation and is reconciled with the authorized subscription. Correcting Subscription funding projection does not match does not change the contractual period, cycle, granted credits or consumption, and does not extend a Trial. Tenant, contract and funding checks remain enforced. For a persistent error, review the existing operation and subscription before repeating registration or checkout.