Overview

Go beyond account-wide branding with per-project client portals. Each client can see a portal branded specifically for them, making ValidGraph invisible and presenting your agency as the sole provider.

How It Works

1. Set up account-wide white-label branding
2. Optionally override branding per project:
– Different logos for different clients
– Custom color schemes per project
3. Viewer users see only the branded portal
4. All reports and exports use the project-level branding

Tier Availability

| Tier | Available |
|——|———–|
| Enterprise | Yes |

Related Features

– White-Label Branding: Account-wide branding settings
– Client Portal: The portal that receives branding
– Viewer Project Scoping: Access control for client users

Mini-Tutorial

Step 1: Set Up Account-Wide Branding

First, configure your white-label branding in Enterprise > White-Label with your company name, logo, and colors.

Step 2: Create Project-Specific Portal

Navigate to Projects > (select project) > Client Portal Settings.

Step 3: Override Branding (Optional)

By default, the portal uses your account-wide branding. Optionally, upload a different logo or colors for this specific client.

Step 4: Invite Client as Viewer

Invite the client as a Viewer with access scoped to this project only.

Step 5: Client Logs In

When the client logs in and views their project, they see your branded portal—not ValidGraph.

Step 6: Share Reports

Generate and email branded PDF reports to the client. Everything displays your company’s branding.

Step 7: Multi-Client Setup

Repeat for each client, optionally customizing branding per client (e.g., white-label for each of their brands).

Technical Details

Get Client Portal Configuration

GET /api/v1/whitelabel/client/proj_abc123
X-API-Key: sk_live_abc123...

Response:

{
  "project_id": "proj_abc123",
  "project_name": "Acme Corp",
  "branding": {
    "inherited": true,
    "company_name": "My Agency",
    "logo_url": "https://cdn.validgraph.io/whitelabel/logo_default.png",
    "primary_color": "#0066CC",
    "secondary_color": "#00CC99"
  },
  "portal_url": "https://portal.validgraph.io/projects/proj_abc123"
}

Configure Project-Specific Branding

POST /api/v1/whitelabel/client/proj_abc123
X-API-Key: sk_live_abc123...
Content-Type: application/json

{
  "override": true,
  "company_name": "Acme Corp (Client-Facing)",
  "primary_color": "#FF6B35",
  "secondary_color": "#004E89"
}

Or upload a client-specific logo:

POST /api/v1/whitelabel/client/proj_abc123/logo
X-API-Key: sk_live_abc123...
Content-Type: multipart/form-data

[file data]

What Viewers See

When a Viewer logs into their project portal, they see:

1. Header: Client-specific or account-wide company logo
2. Dashboard: Project validation scores, trends (with branded colors)
3. Reports: All exports use the project’s branding
4. Notifications: Emails signed with the company name

Per-Project Branding Use Cases

– Agency with Multiple Clients: Each client sees their own “brand”
– White-Label Reseller: Each resold product has distinct branding
– Freelancer Network: Each freelancer’s clients see the freelancer’s brand
– Enterprise Divisions: Different divisions use different colors/logos

Inheritance Behavior

– If override: false (or omitted), portal uses account-level branding
– If override: true, portal uses project-specific branding
– You can switch between inherited and overridden anytime

References

– Multi-Tenant Branding Strategies
– Portal Design Best Practices
– Brand Consistency in SaaS
– ValidGraph White-Label Client Portal API