What are feature flags and how do they control access?

Feature flags are per-brand boolean settings that control which COS capabilities are available to a brand's users. The two primary flags are can_generate, which enables the content generation pipeline (Blog Studio, Webpage Studio), and can_use_titles, which enables AI-generated topic suggestions. An agency might enable full content generation for an active retainer client while keeping it disabled for a prospective client who only needs GEO Intelligence reports. Feature flags are set at the brand level by Admin or Super Admin users and take effect immediately — no deployment or restart required. They provide granular capability control without requiring separate subscription tiers for different service levels.

Multi-Tenant by Design: Agency, Brand, User Hierarchy

Q: How does multi-tenancy keep client data isolated?

COS enforces data isolation at the database level using Supabase Row-Level Security (RLS). Every query — whether it reads campaigns, leads, knowledge entries, or analytics — is filtered by agency_id before results are returned. This is not application-level filtering that could be bypassed by a URL change or API call. RLS policies are attached to the database tables themselves, meaning the database engine rejects unauthorized access regardless of what the application layer requests. Agency A's data is invisible to Agency B at every query, every table, every time. There is no shared workspace, no folder-based separation, and no admin toggle that could accidentally expose one client's data to another.

Q: What can Client-role users see and do?

Client-role users are locked to a single brand via RLS policy and see only that brand's data. They can view GEO Intelligence campaign results and reports, review chatbot analytics, and access published content. If the agency enables the can_generate feature flag, Client users can also use Blog Studio to generate content for their brand. They cannot access other brands within the agency, manage users, modify prompt templates, view billing details, or change platform settings. This design lets agencies give clients direct visibility into their results without risking exposure to internal operations or other clients' data.

Q: Can each brand have its own WordPress site?

Yes. Each brand stores its own WordPress credentials — site URL, authentication token, and SEO plugin preference. When COS publishes content for a brand, it pushes directly to that brand's WordPress installation. An agency managing 10 brands can publish to 10 different WordPress sites from a single COS session, switching between brands via the sidebar selector. WordPress credentials are stored at the brand level and enforced through the same RLS isolation that governs all other brand data, so Brand A's WordPress credentials are invisible to Brand B's users.

Q: How do prompt templates work across brands?

Prompt templates in COS are stage-specific — separate templates for research, draft, style, and SEO phases of content generation. The system provides default templates that work out of the box for any brand. Agencies can then create brand-specific overrides that replace the defaults for individual brands without affecting other brands or the system defaults. Templates support variable injection for brand name, target keywords, context, and URL, so the same template structure adapts to each brand's specifics. If a brand override is deleted or reset, the system default automatically takes its place. Version history tracks all changes, and a one-click reset restores defaults instantly.

Trinzik’s Content Orchestration System (COS) is built from the database up for agencies managing multiple brands. Multi-tenant architecture is enforced by Row-Level Security (RLS) at every query, not application-level filtering.

Three levels: Agency, Brand, User. Each brand has its own WordPress credentials, knowledge base, voice profiles, chatbot configuration, and feature flags. Each user’s role determines data visibility and capabilities.

The Agency Architecture

Agency — top-level billing entity with custom branding, centralized management of all brands and users.
Brand — per-client entity with its own WordPress credentials, SIC code, feature flags, knowledge base, voice profiles, and chatbot config. Categorized as active or prospective. Sidebar selector switches full platform context.
User — authenticated via Supabase Auth with role in app_metadata. Three roles: Super Admin, Admin, Client.
RLS enforcement — every query filtered by agency_id at the database engine level. Client-role users additionally restricted to their assigned brand_id.

Role-Based Access

Role	Scope	Capabilities
Super Admin	Platform-wide	All agencies, brands, users, billing, configuration
Admin	Agency-scoped	All studios, GEO campaigns, leads, outreach, knowledge, templates, billing within agency
Client	Brand-locked	GEO reports (read-only), chatbot analytics, Blog Studio (if `can_generate` enabled)

Each role’s data boundary is enforced by RLS — not by hiding UI elements.

Per-Brand Configuration

WordPress credentials — per-brand site URL, auth token, SEO plugin (Yoast, Rank Math, AIOSEO). Publish to 12 different WordPress sites from one dashboard.
Feature flags — can_generate enables content pipeline, can_use_titles enables topic suggestions. Take effect immediately.
Active/prospective status — run GEO campaigns for prospects to demonstrate value before signing.
Brand switching — sidebar selector changes entire platform context in one click.

Prompt Template Customization

Each pipeline stage (research, draft, style, SEO) uses a distinct template. System defaults work immediately.
Brand overrides replace defaults for specific brands with automatic fallback.
Variable injection populates {{brand_name}}, {{keywords}}, {{context}}, {{url}} at execution time. One-click reset restores defaults.
Version history tracks all changes.

Credit-Based Billing Overview

Every operation costs credits. Credits pooled at agency level with optional Stripe Checkout top-ups.

Pre-flight enforcement blocks operations with insufficient credits (402 response) before AI processing begins. 13 license limits cap brands, users, projects, and operations per tier — counters reset on invoice payment. Stripe Customer Portal manages subscriptions and invoices. Append-only ledger records every transaction for audit.

Full pricing details → /pricing/

Set Up Your Agency

Frequently Asked Questions

How does multi-tenancy keep client data isolated?

Supabase RLS filters every query by agency_id at the database level. The engine rejects unauthorized access regardless of what the application layer requests. Agency A’s data is invisible to Agency B at every query, every table.

What can Client-role users see and do?

Brand-locked via RLS. Can view GEO reports, chatbot analytics, and published content. Blog Studio access if can_generate is enabled. Cannot access other brands, users, templates, or billing.

Can each brand have its own WordPress site?

Yes. Per-brand WordPress credentials (site URL, auth token, SEO plugin). Publish to 10 different sites from one session. Credentials enforced through RLS isolation.

How do prompt templates work across brands?

Stage-specific defaults with brand-level overrides. Variable injection for brand name, keywords, context, URL. One-click reset to defaults. Version history tracks all changes.

Multi-Tenant by Design: Agency, Brand, User Hierarchy

The Agency Architecture

Role-Based Access

Per-Brand Configuration

Prompt Template Customization

Credit-Based Billing Overview

Set Up Your Agency

Frequently Asked Questions

Let's Do This!

Request an AI consultation

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive

Inactive