Qintorava DocsProduct documentation
Form reference

AI provider connections

13 declared fields for AI provider connection. Required fields include Connection name, Provider, Usage scope.

Demo baseline · November 13, 2026
Download PDF

About this form

Use this reference to identify built-in form labels, data types, and validation. Specialized workspaces can render a subset of these fields or provide workflow-specific controls. Your role, record state and tenant configuration can change what you see.

Registry key
ai_provider_connections
Record label
AI provider connection

Field definitions

FieldType or referenceBuilt-in rulesChoices and constraints
Connection name
name		textRequired
Default list field		—
Provider
provider		selectRequired
Default list field		google_vertex_ai, openai, azure_openai, anthropic, custom
Usage scope
scope		selectRequired
Default list field		platform, organization
Project / account
projectOrAccount		textDefault list field—
Usage API base URL
apiBaseUrl		urlOptional by defaultVertex uses the Google Monitoring API. OpenAI: https://api.openai.com. Anthropic: https://api.anthropic.com. Azure OpenAI and custom: public HTTPS adapter URL returning an events array with stable id, occurredAt, model, inputTokens and outputTokens; cost is optional and missing cost is unknown, never free.
Secret Manager credential alias
credentialSecretAlias		textOptional by defaultSecret Manager alias only. OpenAI requires an organization usage/cost admin credential; Anthropic requires a Console organization Admin API key. Vertex uses the runtime identity and Monitoring read permission. Azure OpenAI and custom require your HTTPS usage adapter.
Provider usage API configuration
configuration		provider_configOptional by default—
Connection status
status		selectRead-only
Default list field		Updated only by the live provider connector test and synchronization job.
not_configured, ready, syncing, error, disabled
Last synchronized
lastSyncAt		datetime-localRead-only
Default list field		—
Last connection error
lastError		textRead-only—
Active
active		booleanDefault list field—
Created
createdAt		textRead-only—
Updated
updatedAt		textRead-only—

Lifecycle values

These are stored values from the form definition. Workflow actions can apply additional prerequisites, approvals, and side effects. The workflow determines which transitions are allowed.

FieldValues
Connection statusnot_configured, ready, syncing, error, disabled

Find the procedure and verify the outcome

Verification evidence

The disposable audit exercised 7 applicable validation assertions on this definition. The authenticated collection read returned HTTP 200. See the verification matrix for scope.

Collection read results by built-in role

These statuses were observed over HTTP with one role per disposable MFA account. A successful list response can be empty and does not establish individual record, field, or write access.

RoleHTTP status
Asset Manager403
Change Manager403
CMDB Manager403
Contract manager403
Customer service agent403
Customer service customer403
Customer service manager403
Datacenter Customer403
Datacenter Fulfiller403
Datacenter Manager403
Datacenter Vendor403
EH&S auditor403
EH&S manager403
Executive Reader403
Field service dispatcher403
Field service technician403
HR case agent403
HR knowledge manager403
HR lifecycle manager403
HR profile manager403
Employee Relations investigator403
HR service catalog administrator403
Inventory Counter403
ITIL Fulfiller403
Knowledge Manager403
Business Manager403
Platform Administrator200
Service Desk Agent403
Vendor manager403
Third-party risk manager403
Employee with no workspace role403

Edit and verify

  1. Open the list from the appropriate workspace and select an existing record or a permitted create action. Confirm the intended tenant and record number.
  2. Use the visible controls for the current record type and state. For reference fields, select a returned record from the lookup. Fill visible required fields and use the dedicated workflow action when the record has approval or completion gates.
  3. After saving, reopen the record and compare its persisted values, state and activity to the intended change. Check the downstream linked record when the action creates one.

Troubleshoot

  • Missing field or control: compare the role, module, record state, form conditions and tenant overrides.
  • Lookup returns no result: check that the referenced record is active, in scope and compatible with the current field.
  • Save is rejected: keep the exact validation message and compare the field key, choice, constraints and required related records.
  • See Edit and troubleshoot records and Configuration Studio.