brands
Manage team brands, the logo, colors, and viewer layout your data rooms and links show.
A brand is a named set of viewer settings: logo, banner, colors, welcome message and call to action, data room layout, and the preview card a shared link unfurls into. The team's default brand applies to every data room and link that does not pin another brand or carry its own custom branding. The full model, with the three per-room modes, is in the guide Brand a data room.
$ papermark brands create --name "Acme" --brand-color '#0f172a' --logo ./logo.png --default
✓ Brand created: clxbrand1234567890
{
"id": "clxbrand1234567890",
"object": "brand",
"name": "Acme",
"is_default": true,
"logo_url": "https://…/branding/team_…/logo-abc123.png",
...
}list
papermark brands list [--limit <n>] [--cursor <id>]| Flag | Default | Effect |
|---|---|---|
-l, --limit <n> | 25 | Page size, 1–100 |
-c, --cursor <id> | none | Continuation cursor from a previous response's meta.next_cursor |
--json | auto when piped | Machine-readable output |
$ papermark brands list
ID NAME DEFAULT COLOR LOGO CREATED
clxbrand1234567890 Acme yes #0f172a yes 2026-09-23
clxbrand0987654321 Acme Fund #1d4ed8 2026-09-23Brands come back oldest first.
get
papermark brands get <id>Prints the brand as JSON: every color, image URL, layout, and preview field.
create
papermark brands create --name <name> [--default] [branding flags]| Flag | Default | Effect |
|---|---|---|
-n, --name <name> | required | Brand name, unique within the team |
--default | off | Make this the team's default brand |
Plus any of the branding flags below. The team's
first brand becomes the default even without --default.
Image flags that point at a local file are uploaded one PUT per
image after the brand is created, in the order you passed them. An
https:// URL is sent in the create body instead, and Papermark
downloads it.
papermark brands create \
--name "Acme Fund" \
--brand-color '#1d4ed8' \
--accent-color '#ffffff' \
--logo https://acme.com/brand/logo.png \
--banner ./fund-banner.png \
--welcome-message "Welcome to the Acme Fund data room"update
papermark brands update <id> [--name <name>] [--default] [branding flags]| Flag | Effect |
|---|---|
-n, --name <name> | Rename the brand |
--default | Make this the team's default brand. To move the default, pass --default on another brand |
Patches the brand. Omitted flags stay unchanged; pass "" to clear a
nullable field or remove an image. At least one flag is required.
An update that only carries local image files skips the PATCH and
goes straight to the image uploads.
# Swap the logo, keep everything else
papermark brands update clxbrand1234567890 --logo ./new-logo.png
# Hide the banner on this brand, clear the welcome message
papermark brands update clxbrand1234567890 --banner hidden --welcome-message ""delete
papermark brands delete <id>Deletes the brand and its images. Data rooms and links pinned to it
fall back to the team default. Deleting the default brand promotes
the oldest remaining brand to default. Rooms in custom mode are
unaffected.
Branding flags
The same flags work on brands create, brands update, and
datarooms branding set --mode custom.
Each flag is named after the API field. Pass "" to clear a nullable
field.
Fields
| Flag | Value | Effect |
|---|---|---|
--brand-color <hex> | #rgb or #rrggbb | Primary brand color |
--accent-color <hex> | #rgb or #rrggbb | Background color of the access screen |
--accent-button-color <hex> | #rgb or #rrggbb | Color of the call-to-action button |
--apply-accent-color-to-dataroom-view on|off | Also color the data room list and folder tree with the accent color | |
--hide-logo on|off | Show no logo at all, not even Papermark's | |
--welcome-message <text> | up to 80 chars | Access-screen welcome message. Business or Data Rooms plan |
--cta-label <text> | Call-to-action label. Business or Data Rooms plan | |
--cta-url <url> | https URL | Call-to-action target. Business or Data Rooms plan |
--card-layout GRID|LIST|COMPACT | default LIST | Data room card layout. Data Rooms plan |
--show-folder-tree on|off | default on | Data Rooms plan |
--viewer-layout-preset STANDARD|STRICT|MODERN|NOTION|CUSTOM | default STANDARD | Data Rooms plan |
--viewer-header-style DEFAULT|SPLIT|NOTION | default DEFAULT | Data Rooms plan |
--hide-folder-icons-in-main on|off | default off | Data Rooms plan |
--default-language <code> | en, de, fr, es, it, nl, pt-BR, ja | Viewer language. Anything other than en needs a Data Rooms Plus plan. Cannot be cleared |
--custom-link-preview-enabled on|off | Unfurl shared links with the custom title, description, image, and favicon. Business or Data Rooms plan | |
--link-preview-title <text> | up to 120 chars | |
--link-preview-description <text> | up to 240 chars |
Setting a field back to its default value is never plan-gated. Enum values are accepted in any case and uppercased.
Images
Each image flag takes a local file path, an https:// URL, or ""
to remove the image.
| Flag | Accepted | Max size | Extra |
|---|---|---|---|
--logo <path|url> | .png, .jpg, .jpeg | 2 MB | |
--banner <path|url> | .png, .jpg, .jpeg | 4 MB | --banner hidden hides the banner |
--link-preview-image <path|url> | .png, .jpg, .jpeg | 4 MB | 1200x630 recommended. Business or Data Rooms plan |
--link-preview-favicon <path|url> | .png, .ico | 1 MB | Business or Data Rooms plan |
The CLI checks local files before sending anything: the extension
must be one of the accepted ones (the content type comes from the
extension), the file must be non-empty, and it must be under the
slot's cap. Non-https URLs are rejected. No SVG or WebP.
With --dry-run, a binary request body is summarized as
<N bytes image/png from ./logo.png> instead of printed, and
brands create shows the upload against the placeholder id :id
because no brand exists yet.
Required scopes
| Operation | Scope |
|---|---|
list, get | branding.read |
create, update, delete | branding.write |
papermark login requests both by default. A session created before
these scopes existed needs a fresh papermark login.
Related
datarooms branding: choose which brand a data room shows, or give it custom branding- Guide: Brand a data room: the model and the worked recipe across CLI, API, and MCP
- API: Branding: the endpoints behind these commands
- MCP: Branding tools: the same surface for agent-driven workflows