---
title: "Branding Templates"
description: "Create reusable branding for reports, email, SMS, and audio delivery"
canonical: https://y2.dev/docs/profiles/branding/
---

Information Operations

# Branding Templates

Create reusable branding for reports, email, SMS, and audio delivery

Branding templates let a Pro or Elite workspace reuse its logo, colors, terminology, and delivery copy across intelligence profiles.

Branding requires an active **Pro** or **Elite** workspace. Pro supports up to **10** templates. Elite supports up to **100**.

## Create and assign a template

### Open Branding

Open **InfoOps → Branding**. Select **New Template**.

### Name the template

Use a name that identifies where the branding belongs, such as “Company Briefings” or “Client Deliverables.” A template name can contain up to 50 characters.

You can also mark the template as the workspace default. Only one template can hold that marker at a time.

### Configure the output

Add only the elements you need. Any omitted values fall back to Y2 defaults.

| Area            | Available settings                                         |
| --------------- | ---------------------------------------------------------- |
| Visual identity | Logo, logo alt text, header color, accent color            |
| Terminology     | Report type and analyst role                               |
| Delivery copy   | Email preview prefix, SMS prefix, audio intro, audio outro |
| Static content  | Optional content before or after a report                  |

### Save the template

Resolve any validation errors. Select **Save**.

### Assign it to a profile

Create or edit a profile. Open **Advanced**. Select the branding template. Save the profile. Y2 applies the template when it renders or delivers a report.

The **Set as Default** marker is unique, but the current profile editor still requires you to select a branding template explicitly. Verify the assignment in **Advanced** instead of relying on the default marker alone.

## Visual identity

### Logo

The branding editor accepts PNG, JPEG, SVG, and WebP files up to 2 MB. Add meaningful alt text for recipients who cannot see the image.

| Property      | Enforced limit |
| ------------- | -------------- |
| File size     | 2 MB           |
| Logo alt text | 100 characters |

Use a wide logo with a transparent background. Preview a delivered email. Check that the logo is legible at small sizes.

### Colors

Header and accent colors accept three- or six-digit hex values, such as `#05c` or `#0055cc`. Values are normalized when the template is saved.

Use only hex colors. Invalid values are rejected by server-side validation.

## Terminology and delivery copy

Use `{name}` in supported text fields to insert the assigned profile's name.

| Field                | Character limit | Default                          |
| -------------------- | --------------- | -------------------------------- |
| Report type          | 30              | Briefing                         |
| Analyst role         | 50              | professional analyst             |
| Email preview prefix | 30              | Your Briefing:                   |
| SMS prefix           | 20              | `{name}:`                        |
| Audio intro          | 100             | Welcome to your {name} briefing. |
| Audio outro          | 200             | Y2 closing message               |

For pronunciation rules that apply to names, acronyms, or technical terms, use a [pronunciation dictionary](https://y2.dev/docs/audio#create-a-pronunciation-dictionary).

## Add static content

Each template can place one content block before the report and another after it. A block can use the `callout`, `highlight`, or `sponsor` style and can contain channel-specific copy.

| Content    | Enforced limit | Used by                   |
| ---------- | -------------- | ------------------------- |
| Label      | 30 characters  | Block heading             |
| HTML       | 500 characters | Email and rendered report |
| Audio text | 200 characters | Audio narration           |

The `{name}` placeholder is supported in the label, HTML, and audio text.

Use the limits in the table above. Y2 rejects larger values even if the editor counter shows a larger allowance.

Static HTML is sanitized before it is stored and rendered. Scripts, embedded forms, event handlers, unsafe URLs, iframes, and similar executable elements are removed. Use simple formatting and links rather than interactive markup.

## Update or remove a template

Assigned profiles reference the template rather than copying it. Changes therefore affect subsequent renders and deliveries from every profile using that template.

To delete a template:

### Find assigned profiles

Edit each profile that uses the template.

### Remove or replace the assignment

Select another template or clear the branding selection, then save the profile.

### Delete the template

Return to **InfoOps → Branding**. Select **Delete**. Confirm the deletion.

The backend rejects deletion while any profile still references the template. Unassign every profile first, even if the confirmation dialog suggests that profiles will fall back automatically.

## API boundary

The public profile create and update schemas expose `brandingTemplateId`. Use the generated [Profiles API reference](https://y2.dev/docs/api/reference/profiles) for the canonical request schema and required scopes.

Creating, editing, and deleting branding templates is currently an app-only workflow. Dedicated branding-management endpoints are not part of the public OpenAPI document.

## Plan limits

| Plan  | Templates | Logo upload |
| ----- | --------- | ----------- |
| Free  | 0         | No          |
| Lite  | 0         | No          |
| Pro   | 10        | Yes         |
| Elite | 100       | Yes         |

## Next steps

[Create a profile](https://y2.dev/docs/profiles/creating): Configure a profile and assign the template.

[Configure email delivery](https://y2.dev/docs/delivery/email): Review how generated reports reach recipients.

[Review plans and limits](https://y2.dev/docs/plans): Compare workspace capabilities and quotas.
