Skip to main content
AI Workflow Center
Get Template — $89

Search AI Workflow Center

Search tools, categories, stacks, and pages

Guides

Configuration

Site identity, domains, roles, credentials, schedules, and publication policy.

V03 separates deployment configuration from Site configuration.

Deployment variables identify infrastructure and secrets: database roles, hosts, auth, R2, Polar, browser worker, Turnstile, Push, and the immutable release descriptor. They change through the deployment secret store.

Site configuration identifies a logical branded directory inside that deployment: name, copy, color, links, analytics, recipe, task schedules, provider endpoints, policy packages, and display price. It changes through the Site-scoped admin console.

Sites and domains

/admin/sites creates an isolated Site as inactive. Production activation requires ownership proof through a DNS TXT record at _awp-site-verification.{host}. The Host enters tenant resolution only after verification and exactly one canonical domain is selected.

Each buyer still runs a separate deployment. Multiple Sites inside that deployment share infrastructure but not data access: forced row-level security, composite foreign keys, Host resolution, membership checks, cache keys, object keys, and queues all include the Site boundary.

Membership roles

  • owner controls the Site and cannot be removed or demoted through normal operations.
  • admin manages members, settings, credentials, keys, content, and tasks.
  • editor creates and edits draft content.
  • reviewer makes publication and model-output review decisions.
  • viewer has read-only console access.

The role belongs to SiteMembership, not the global User identity. Removing a membership does not delete the person or access they may hold on another Site.

Credential references

Register references in /admin/settings. A valid reference uses the env:NAME form, must appear in ALLOWED_SECRET_REFS, and must resolve in the server environment. The console never accepts or returns the secret value.

Revoking a reference also deactivates dependent datasources in the same transaction.

Datasources and recipes

Datasource versions are immutable. A new version must declare source URL, rights basis, license reference, deletion policy, and optional retention. Activating a version deactivates the prior version with the same name.

Site Recipes use the awp-site-recipe@1 contract. Imports reject secret-bearing fields, malformed package digests, missing rights, and incompatible engine versions. Only reviewed, published versions appear in the Gallery.

Publication

Links, Dimensions, content, page templates, and recipes follow a forward-only lifecycle: DRAFT → REVIEW → PUBLISHED → ARCHIVED. Editing an item in review invalidates that review and returns the item to draft. Archived records are immutable; create a replacement version instead of reviving them.

Public reads require both PUBLISHED and an allowed availability state. An active Tool extension alone does not make its Link public.