Skip to main content

Account, Trial, And Subscription

Document.Bot uses account sign-in and device activation. It does not use manual license keys.

Account Sign-In​

Document.Bot signs in through the browser using OAuth. After browser sign-in succeeds, the desktop app activates the current device for your account or organization.

If you belong to more than one organization, you may need to choose which organization to activate.

Device Activation​

Your account may have a device limit. If activation would exceed the limit, Document.Bot should show a device-management recovery link.

Signing out or restarting onboarding may clear the current account connection on this device.

Subscription And Billing State​

Some app actions can depend on your subscription state, organization access, or account usage limits.

If access is blocked, Document.Bot should explain the reason and offer a recovery action such as opening billing, upgrading, refreshing account state, or managing devices.

Billing states such as past due, unpaid, or canceled may have a short grace period before blocking applies.

Self-Serve Plans And Enterprise Help​

Self-serve plans are for standard Document.Bot access, standard terms, and card checkout.

Contact the Document.Bot team when your organization needs a guided pilot, procurement review, a security or privacy discussion, invoice or purchase-order handling, company login or SSO scoping, custom deployment planning, or a quote before rollout.

Usage Limits​

Account settings can show usage limits and remaining availability. These labels should be user-facing, such as Hosted AI or AI Search/Index credits, rather than backend quota names.

Usage can apply separately to:

  • BYO or local AI usage
  • Document.Bot managed hosted AI
  • hosted indexing or search

What API Keys Do Not Do​

Provider API keys are for AI providers. They do not grant Document.Bot subscription access, device activation, or account entitlement.

Last updated on