Ovok platform resource types

The inspected sandbox schema includes these 16 non-FHIR platform types in addition to the 146 FHIR R4 resources. Their presence in introspection describes the schema; it does not make them application data models or grant access. Use FHIR resources for clinical data, and use the Console and linked platform references for project configuration and account workflows.

For each type, the table lists the read-by-ID field, list field, connection field, resource-specific list arguments, and available CRUD mutations. Shared list arguments are documented in queries and pagination.

Ovok type	Read, list, connection fields	Resource-specific list arguments	Mutations
AccessPolicy	AccessPolicy(id: ID!) AccessPolicyList AccessPolicyConnection	name	AccessPolicyCreate AccessPolicyUpdate AccessPolicyPatch AccessPolicyDelete
Agent	Agent(id: ID!) AgentList AgentConnection	identifier, name, status	AgentCreate AgentUpdate AgentPatch AgentDelete
AsyncJob	AsyncJob(id: ID!) AsyncJobList AsyncJobConnection	type, status	AsyncJobCreate AsyncJobUpdate AsyncJobPatch AsyncJobDelete
Bot	Bot(id: ID!) BotList BotConnection	identifier, name, category, cds_hook	BotCreate BotUpdate BotPatch BotDelete
BulkDataExport	BulkDataExport(id: ID!) BulkDataExportList BulkDataExportConnection	status	BulkDataExportCreate BulkDataExportUpdate BulkDataExportPatch BulkDataExportDelete
ClientApplication	ClientApplication(id: ID!) ClientApplicationList ClientApplicationConnection	name	ClientApplicationCreate ClientApplicationUpdate ClientApplicationPatch ClientApplicationDelete
DomainConfiguration	DomainConfiguration(id: ID!) DomainConfigurationList DomainConfigurationConnection	domain	DomainConfigurationCreate DomainConfigurationUpdate DomainConfigurationPatch DomainConfigurationDelete
JsonWebKey	JsonWebKey(id: ID!) JsonWebKeyList JsonWebKeyConnection	active	JsonWebKeyCreate JsonWebKeyUpdate JsonWebKeyPatch JsonWebKeyDelete
Login	Login(id: ID!) LoginList LoginConnection	user, code, cookie	LoginCreate LoginUpdate LoginPatch LoginDelete
Project	Project(id: ID!) ProjectList ProjectConnection	identifier, name, owner, google_client_id, recaptcha_site_key	ProjectCreate ProjectUpdate ProjectPatch ProjectDelete
ProjectMembership	ProjectMembership(id: ID!) ProjectMembershipList ProjectMembershipConnection	project, user, profile, profile_type, user_name, external_id, access_policy, identifier, active	ProjectMembershipCreate ProjectMembershipUpdate ProjectMembershipPatch ProjectMembershipDelete
SmartAppLaunch	SmartAppLaunch(id: ID!) SmartAppLaunchList SmartAppLaunchConnection	—	SmartAppLaunchCreate SmartAppLaunchUpdate SmartAppLaunchPatch SmartAppLaunchDelete
SubscriptionStatus	SubscriptionStatus(id: ID!) SubscriptionStatusList SubscriptionStatusConnection	—	SubscriptionStatusCreate SubscriptionStatusUpdate SubscriptionStatusPatch SubscriptionStatusDelete
User	User(id: ID!) UserList UserConnection	identifier, email, external_id, project	UserCreate UserUpdate UserPatch UserDelete
UserConfiguration	UserConfiguration(id: ID!) UserConfigurationList UserConfigurationConnection	name	UserConfigurationCreate UserConfigurationUpdate UserConfigurationPatch UserConfigurationDelete
UserSecurityRequest	UserSecurityRequest(id: ID!) UserSecurityRequestList UserSecurityRequestConnection	user	UserSecurityRequestCreate UserSecurityRequestUpdate UserSecurityRequestPatch UserSecurityRequestDelete

Security-sensitive fields

Some platform object types can contain authentication, credential, key, or user-security data. Introspection reveals field names, not authorization. Do not select, return, or log secrets, password material, MFA data, tokens, or private key material from a general application. Use the documented Authentication, Access policies, and Settings and features flows instead.