Before you begin
Confirm account, tenant and active role in the account menu. Inspection requires view permission; changing records requires the specific management permission. A hidden or disabled action can reflect authorized scope; do not switch tenants to evade a denial. Work only with records in the workspace you are allowed to administer.
Procedure
- Open Subscription & billing and select Tenant.
- Review Subscription and the billing profile.
- Use DPU & calculator for estimates and Payments & invoicing for permitted merchant configuration.
- Inspect Licenses, Commerce, Global catalog and Tenant offers according to your responsibility.
Behavior and limits
The seven tabs separate contracts, usage, payments and catalog. DPU measures capacity; DPU-h multiplies capacity by active time. Development and Production have separate funding and concurrency. Tasks aggregate usage; the Workflow is not charged again.
Queued work and structural validation are not billable. Purchased concurrency does not create workers. Accepted DovaAI queries have tenant and user quotas separate from DPU. A browser return or manual invoice status does not prove confirmed payment.
Calculation example: 4 DPU for 15 minutes consumes 1 DPU-h. Credits follow verified funded periods, not necessarily calendar months. A payment or fiscal-document sandbox does not establish production acceptance.
Verify the result
After saving or confirming, reopen the detail and check the state reported by the server. Distinguish an accepted request from a completed operation and retain only minimal evidence without sensitive information. When an operation is pending, wait for its final state in the corresponding view before starting another action on the same object.
Laboratory example
Use the synthetic tenant documentation-lab and, where relevant, worker worker-demo-a. Note the previous state, perform one authorized action and compare the resulting state. These names illustrate the procedure; they do not identify production records or authorize creating cloud resources. For a review without changes, inspect the detail and cancel any open form.
If something fails
If a conflict appears, refresh the inventory and review current values before repeating. If the session expired, sign in and complete MFA when required. For a permission error, check the role and membership; for a provider error, inspect the operation and its safe message. Do not alter storage, revisions or controls to force an outcome.
Related reading
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.
Without an explicit pool, Production does not borrow Development capacity and new jobs do not run through an implicit default. 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.
Funding projection and period
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.