Data model

The provider exposes read-only compliance views and explicit stored procedures. Views do not support INSERT, UPDATE, or DELETE. You can permanently delete data only through the Delete* procedures.

Activity Feed design

Activities is the forward-compatible Activity Feed view. It flattens only Id, CreatedAt, OrganizationId, OrganizationUuid, and Type. Actor is the complete discriminated actor object as JSON. EventDetails is the complete source activity object as JSON, including type-specific fields. This preserves new activity and actor shapes without a driver update.

The priority typed activity views, such as AccountDeleted and ClaudeFileUploaded, expose selected activity types with their relevant top-level fields. They use a fixed activity type and flatten the documented actor union into nullable Actor* columns. Use CreateActivitySchema when you need a typed view for an activity type that does not have a built-in view. The generated view reflects one sampled activity, so regenerate it when Anthropic adds type-specific fields you need.

Query behavior

Views use API pagination automatically. Views backed by per-parent API paths can obtain their path values from the related parent view when the path column is omitted. Server-side filter support, query examples, automatic path expansion, and API-specific limits are documented on each individual view page. Procedure inputs, outputs, and EXEC examples are documented on each stored procedure page.

Time filters map to the API range parameters created_at.gte, created_at.gt, created_at.lt, and created_at.lte, and to the matching updated_at forms. The API models a time filter as a range only, so a date column supports >, >=, <, and <=. The component evaluates equality comparisons on a date column after retrieval.

Chats supports one ascending CreatedAt or UpdatedAt server-side order key. All Activity Feed views, including views generated by CreateActivitySchema, support one CreatedAt key in either direction. Activity views omit the API order parameter when SQL has no ORDER BY, preserving the API's newest-first default. The component performs every unsupported, non-timestamp, or multi-column ORDER BY after retrieval. When the API cannot perform an ORDER BY, the component follows every page using the maximum page size, then applies the requested ordering and LIMIT client-side. A query that combines ORDER BY with LIMIT on such a view therefore reads the full filtered result set before returning rows. Add server-side filters to keep that result set small.

When using ascending activity order with an incremental cursor, late-arriving activities can fall behind that cursor. Workloads that require at-least-once delivery should periodically requery an overlapping CreatedAt range and deduplicate by Id.

Views lists all available views and their columns. Stored Procedures lists all stored procedures and their inputs and outputs.