01 / SSO BRAND SYSTEM
One system. A clear identity.
Our visual system combines neutral surfaces, purposeful color, clear typography, and consistent spacing. These guidelines explain how to use that system alongside approved SSO logos and partner materials.
Clarity first
Build with a structured grid, square-edged surfaces, clear hierarchy, and restrained color. Keep familiar controls and interaction patterns consistent across experiences.
A consistent identity
Use the SSO name, approved artwork, and identity blue as the brand layer. Brand styling must not obscure content, interaction states, or accessibility.
Accessible by design
Aim for WCAG AA: at least 4.5:1 for ordinary text and 3:1 for large text and essential interface graphics. Preserve visible keyboard focus.
02 / SSO BRAND SYSTEM
Logo usage
Use approved SSO artwork, never a recreation. These examples demonstrate the existing square SSO logo; other supplied variants must retain their own artwork and background.

Allowed
Use the original artwork
Keep the complete logo, its original proportions, and the supplied background.

Allowed
Give the logo room
Leave clear space on every side. As a working guide, allow at least one quarter of the logo width.

Not allowed
Do not stretch
Never compress, widen, or change the relationship between elements.

Not allowed
Do not rotate
Keep the supplied logo upright. Do not tilt, skew, or add perspective.

Not allowed
Do not recolor
Do not apply filters, gradients, shadows, outlines, or substitute colors.

Not allowed
Do not crop
Do not cut off the mark or wordmark, separate its parts, or obscure it with other content.
Keep the logo readable at its final size. Use the correct light or dark asset from the portal instead of altering it. If no suitable asset exists, request approval through the Partner Portal.
03 / SSO BRAND SYSTEM
Color & hex values
Neutral grays organize the interface. Blue identifies actions and links, while supporting colors communicate status. SSO blue adds brand identity without changing the meaning of interface colors.
SSO identity
SSO blue
#00267D
SSO identity accent. Keep original logo colors unchanged.
Interface foundation
Blue 60
#0F62FE
Primary interface actions, not a substitute logo color.
Interface foundation
Gray 100
#161616
Page background in the dark theme.
Interface foundation
Gray 90
#262626
Raised surfaces and grouped content.
Interface foundation
Gray 10
#F4F4F4
Primary text on dark backgrounds.
Interface foundation
Gray 30
#C6C6C6
Secondary text on dark backgrounds.
Status color
Green 40
#42BE65
Allowed examples and positive status only.
Status color
Red 50
#FA4D56
Not-allowed examples and errors only.
Applying the palette
01
Organize with neutrals
Use subtle changes in gray to separate the page, grouped content, and nested surfaces. Keep bright color purposeful rather than using it as decoration.
02
Give colors stable roles
Use blue for primary actions and links. Reserve green for positive status and red for errors or prohibited examples. A color’s meaning should remain the same across pages and themes.
03
Layer light surfaces
Use White #FFFFFF or Gray 10 #F4F4F4 as the base. Alternate those two values as surfaces are nested, instead of introducing arbitrary midtone backgrounds. Use dark text on light surfaces.
04
Layer dark surfaces
Use Gray 100 #161616 or Gray 90 #262626 as the base. Make nested surfaces progressively lighter, moving through #262626, #393939, and #525252 as needed. Avoid darker nested panels unless deliberately creating a high-contrast treatment.
05
Use contrast intentionally
A light element on a dark surface, or a dark element on a light surface, can highlight important content. Preserve legible text, visible boundaries, and clear focus states instead of adding contrast for decoration.
06
Separate roles from values
Name reusable colors by purpose, such as background, layer, text-primary, link, or support-error. When switching themes, change the value assigned to the role, not what the role means.
Check every foreground and background pairing. Ordinary text needs at least 4.5:1 contrast; large text and essential interface graphics need at least 3:1. Pair status colors with words and icons, and never recolor a supplied logo to match a theme.
Supporting values: White #FFFFFF for supplied light assets, Gray 60 #525252 for borders, and Blue 40 #78A9FF for links on dark surfaces. Use semantic tokens in interfaces. Do not use color alone to communicate meaning; pair it with a label and icon.
04 / SSO BRAND SYSTEM
Typography & spacing
Use the type and spacing scales below to keep communication calm, legible, and consistent.
TYPEFACE / IBM PLEX SANS
Clarity comes first.
Use light (300) for expressive headings, regular (400) for body copy, and semibold (600) for labels. Keep body text neutral and use clear, descriptive link labels.
12 · 14 · 16 · 20 · 24 · 32 · 48
Selected type sizes, in pixels.
SPACING / STANDARD SCALE
Room to breathe.
Align content to a shared grid. Use consistent spacing to group related information, and larger gaps to distinguish sections. Avoid decorative clutter around logos.
2 · 4 · 8 · 12 · 16 · 24 · 32 · 48 · 64
Selected spacing increments, in pixels.
05 / SSO BRAND SYSTEM
Partner assets & co-branding
Approved partners can access the logo library in the Partner Portal. Use the assets and any usage conditions supplied there; access to the library does not grant unrestricted trademark rights.
Keep the relationship clear
On a partner’s own materials, keep the partner identity primary and the SSO identity secondary unless an approved agreement specifies otherwise. Give each logo independent clear space and a separate area of the layout, such as opposite corners. Do not place logos directly next to one another, merge marks into a new logo, imply ownership, or claim certification or endorsement without authorization; use a direct lockup only when that exact arrangement is expressly approved.
Use “SSO Artists Entertainment” in full on first mention. Use relationship wording only when it accurately reflects your agreement. Third-party logos and certification badges require their owners’ separate permission.
06 / SSO BRAND SYSTEM
Logotypes, clear space & size
Make the identity easy to recognize in every medium. Use the supplied files as artwork, and use the company name as ordinary text in copy.
Artwork and written names
Use the current approved horizontal wordmark when a horizontal identity is needed, and the supplied square asset for square placements. Do not rebuild either with type or combine separate parts. In headlines and sentences, type SSO Artists Entertainment as text rather than inserting a logo in place of words.
A protected area
For a horizontal wordmark, let X equal the height of the SSO mark and keep at least X clear on every side. For the square artwork shown above, X is one quarter of its width. Keep photography, type, borders, and other identities outside this area. More breathing room is preferred.
Minimum reproduction sizes
For horizontal artwork, use a minimum height of 22 CSS pixels on screen, with at least 44 image pixels for a 2x export, or 5 mm in print. For the detailed square artwork, start at 88 CSS pixels and increase it whenever the lettering is difficult to read. These are minimums, not preferred display sizes. Never enlarge a low-resolution file.
Separate brand placements
Use one SSO identity per individual promotional layout. A partner logo belongs in a separate region, such as an opposite corner, with its own clear space. Do not place it immediately beside the SSO mark or brand name to suggest a combined identity. A different arrangement requires an expressly approved lockup.
Keep the mark unchanged
Do not animate, rotate, tilt, stretch, crop, recolor, redraw, or decorate the logo. Do not add a product name, release number, version, slogan, or partner name to the artwork. Select an approved background variant instead of editing the file.
WRITTEN-NAME EXAMPLE
Our team introduces an integration with SSO Artists Entertainment.
Use this sentence structure only for a real, approved integration. Do not replace the written name with a logo image.
07 / SSO BRAND SYSTEM
Campaign assets & formats
Use these production specifications for SSO marketing. Dimensions below are in pixels and describe the required outputs, not a claim that every downloadable asset already exists.
Website tiles
625 × 795; 571 × 338; 416 × 270; 200 × 150
Pair every tile with explanatory live text. The smallest format is for a logo-only treatment, not a compressed campaign.
Social posts
1080 × 1080 (1:1); 1080 × 1350 (4:5); 1080 × 1920 (9:16)
Compose for square, portrait, and full-screen placements separately. Keep essential type and branding clear of platform overlays and cropping.
Email banners
1472 × 828 desktop; 640 × 360 mobile
Use a single audience-relevant banner. Both versions are 16:9; preserve the proportions and check readability at the actual display size.
Website hero banners
2880 × 1152; 1536 × 614; 720 × 300
Place near the top of the campaign page with balanced margins. Build a dedicated mobile composition rather than cropping away the message.
Digital display banners
320 × 250; 728 × 90
Use one concise benefit and one destination. A 300 × 250 placement may need a separate export; confirm the booked dimensions rather than stretching the 320 × 250 file.
Animated GIFs
300 × 300; 600 × 600
Animate supporting campaign elements, not the SSO logo. Keep the main message understandable in a still frame, avoid flashing, and provide a static alternative.
Choose the audience first. For studios, venues, offices, and other physical operations, use imagery that reflects the actual setting. For online-only artists, labels, and media businesses, show relevant digital or creative work without implying a walk-in location.
Choose the treatment second. An approved photo with the supplied identity can introduce a specific story. Photography alone needs adjacent brand identification and copy. A non-photographic treatment works for a broad platform overview. Use only images, artwork, and likenesses cleared for the campaign.
Release only finished assets. Draft photography, temporary copy, and pending retouching are not approved for publication. Check the file version, territory, channel, usage period, permissions, crop, and destination before release. Request missing variants through the Partner Portal instead of adapting restricted artwork.
08 / SSO BRAND SYSTEM
Voice, naming & messaging
Be direct, useful, and specific. Start with the creator’s or partner’s goal, then explain the relevant service and the next step. The examples here are starting points for review, not automatic approval for every campaign.
Write names consistently
- Use SSO Artists Entertainment in full on first mention. SSO is acceptable afterward when the meaning is clear.
- Preserve the spelling, spacing, and capitalization of SSO Gateway, SSO Digital Solutions, SSO Node, SSO Broadcast, SSO Intelligence, and White Distribution.
- Do not invent product abbreviations or attach version numbers to brand artwork. Keep names unchanged in translated copy unless an approved localized name is supplied.
- Use the company’s documented legal entity name only where legal identification is required. Do not invent a corporate suffix.
Make the benefit credible
- Explain one useful outcome without promising success, earnings, playlist inclusion, or guaranteed placement.
- Support statistics with current evidence, scope, source, and date. Do not reuse another company’s performance percentages.
- Do not speculate about future releases, imply unconfirmed integrations, or describe planned features as available.
- State eligibility, region, pricing, and feature limitations where they affect the offer. Check current service documentation before publishing.
- Use plain language, descriptive links, and short sentences. Avoid exaggerated claims, artificial urgency, and em dashes.
Headline directions
- Creative ambition. Supported by infrastructure.
- Build the next chapter of your catalog.
- Connect your release plans with the systems behind them.
- A clearer path from creative work to delivery.
SHORT DESCRIPTION
SSO Artists Entertainment brings label, publishing, and media infrastructure services together for creators and industry partners.
LONG DESCRIPTION
SSO Artists Entertainment supports work across music, film, television, and podcasting. Its creative and technical services span artist development, publishing, distribution infrastructure, and media systems. Creators and partners can explore the services relevant to their work, with the scope, eligibility, and terms confirmed for each engagement. Creative stewardship and technical distribution remain distinct, so communications should explain which service a particular relationship includes.
09 / SSO BRAND SYSTEM
Service-specific copy playbook
Use the appropriate message for the actual service. These headline, short-copy, and longer-copy directions cover discovery, campaigns, actions, communications, transactions, reporting, and promotion without inventing product capabilities.
SSO Gateway / distribution
- HEADLINE
- Prepare your music for its next destination.
- SHORT COPY
- Explore distribution infrastructure for your catalog.
- LONGER COPY / REQUIRED CONTEXT
- Describe the applicable release workflow, metadata requirements, delivery destinations, and support scope. Explain what the partner contributes and what SSO handles. Do not promise acceptance, delivery timing, or editorial placement without confirmed terms.
Publishing & rights
- HEADLINE
- Give your rights a clear foundation.
- SHORT COPY
- Explore publishing support for your creative work.
- LONGER COPY / REQUIRED CONTEXT
- Explain the publishing or rights-administration service included in the engagement, what rights remain with the creator, and any registration or reporting responsibilities. Never imply that distribution alone grants publishing representation or guarantees collection.
Announcements & campaigns
- HEADLINE
- Put the next release in focus.
- SHORT COPY
- Introduce a release, event, or service update with one clear story.
- LONGER COPY / REQUIRED CONTEXT
- State what is new, who it serves, when it is available, and where to learn more. Use cleared cover artwork or photography, a concise description, and one relevant destination. Do not describe a planned campaign tool as a live SSO product.
Calls to action
- HEADLINE
- Help people take the next step.
- SHORT COPY
- Choose a clear action, such as exploring services or applying to partner.
- LONGER COPY / REQUIRED CONTEXT
- Match the action to the destination. A release link should open the relevant release, a partner invitation should lead to the Partner Portal, and an inquiry should reach the correct contact route. Do not claim ticketing, reservations, or ordering integrations unless actually supported.
Branded communications
- HEADLINE
- Make every message recognizably SSO.
- SHORT COPY
- Use a consistent name, approved identity, and clear sender.
- LONGER COPY / REQUIRED CONTEXT
- Present the correct company or partner identity in newsletters and service communications. Use accurate sender details and a recognizable destination. Branding by itself does not establish email verification or provide a third-party branded-mail feature.
Payments & receipts
- HEADLINE
- Keep the transaction clear.
- SHORT COPY
- Identify the business and describe the purchase accurately.
- LONGER COPY / REQUIRED CONTEXT
- Where a payment service is part of the confirmed offer, keep business names, payment descriptions, and receipts consistent. Obtain approval for any payment-provider artwork. Do not imply an SSO payment product, wallet integration, or device-specific checkout capability without confirmation.
SSO Node / reporting
- HEADLINE
- See the story behind your catalog.
- SHORT COPY
- Explore catalog, royalty, and release reporting in SSO Node.
- LONGER COPY / REQUIRED CONTEXT
- Explain which reports are available for the user’s service and data coverage. Identify reporting periods, delays, and limitations. Do not promise real-time accuracy, competitor comparisons, or a specific performance increase unless those claims are documented.
Promotion & advertising
- HEADLINE
- Give your campaign a clear destination.
- SHORT COPY
- Plan promotion around the audience and the release.
- LONGER COPY / REQUIRED CONTEXT
- Describe only the campaign channels, budgets, dates, and territories that have been confirmed. Separate paid promotion from organic distribution. Never transfer another provider’s ad features, launch dates, or regional availability into an SSO offer.
SSO Digital Solutions / White Distribution
- HEADLINE
- Build around your own brand.
- SHORT COPY
- Explore custom media systems and distribution infrastructure.
- LONGER COPY / REQUIRED CONTEXT
- Explain the agreed engineering, API, metadata delivery, and platform scope. Clarify which party operates the service, owns the customer relationship, and supports end users. Do not imply that every integration or feature is included in every engagement.
SSO Broadcast / SSO Intelligence
- HEADLINE
- Connect creative work with specialist systems.
- SHORT COPY
- Explore media delivery and intelligence services for your needs.
- LONGER COPY / REQUIRED CONTEXT
- For SSO Broadcast, describe the confirmed video-delivery or facilitation scope. For SSO Intelligence, explain the specific analysis being offered and its limitations. Neither distribution access nor predictive analysis guarantees a platform deal, audience result, or valuation.
10 / SSO BRAND SYSTEM
Email & website layout templates
Follow these composition recipes when creating campaign materials. These are on-page layout references, not downloadable production artwork or automatically sent emails.
Email composition
- Start with a short subject line, placing the important information first so it survives truncation.
- Use one key visual chosen for the audience, with even margins. Choose a non-photographic banner for a general introduction.
- Lead with one feature or benefit. Follow with brief live text that still works when images are blocked.
- End with one clear call to action linked to the relevant, current destination. Check the mobile layout, alternative text, and any required terms.
Website & display composition
- Use a 12-column grid on wide screens, adapting to fewer columns on smaller screens.
- Place a campaign hero near the top, using the 2880 × 1152, 1536 × 614, or 720 × 300 composition appropriate to the placement.
- Center a 728 × 90 banner within the grid with clear space around it. Do not let it compete with navigation or key page actions.
- Position portrait, landscape, and 200 × 150 logo-only tiles to suit the surrounding content. Left and right alignment are both acceptable when grid edges and margins stay consistent.
- Keep explanatory text next to tiles. Recompose for narrow screens rather than shrinking words or distorting artwork.
HERO / FULL GRID
Creative ambition. Supported by infrastructure.
One audience, one core benefit, one relevant destination.
Centered supporting banner
The same restraint applies to social and animated formats: one lead message, sufficient contrast, a readable identity, and a destination that matches the promise. Keep logos static even when other campaign elements move.
11 / SSO BRAND SYSTEM
Marketing approval & press
Approval protects the clarity of the relationship and the accuracy of the message. Complete the review before scheduling or publishing a campaign.
01 / REVIEW
Submit before publication
Marketing that promotes or refers to SSO, including partner announcements, landing pages, email, paid ads, social posts, and public campaign assets, requires written SSO approval before it goes live. Route requests through your SSO partner contact or the Partner Portal.
02 / REVIEW
Allow review time
Send press releases, blog drafts, and intended media lists at least two weeks before the proposed announcement. Include finished visuals, copy, destinations, intended channels, audience, territories, usage dates, and the relevant agreement. Submission is not approval and does not guarantee a turnaround.
03 / REVIEW
Describe the actual relationship
Focus PR on the integration or service that has been agreed and the specific customer benefit it supports. Explain each party’s role clearly. Do not imply an acquisition, exclusive arrangement, certification, endorsement, or broader partnership than the agreement allows.
04 / REVIEW
Leave statements to their owner
Do not speak on behalf of SSO or another partner. Refer journalist inquiries about SSO to the designated SSO communications or partner contact. Do not invent executive quotations, official endorsements, or company boilerplate; use only text expressly cleared for the announcement.
05 / REVIEW
Approve the final version
Keep a record of the written approval and the exact materials it covers. Material changes to wording, artwork, placement, offer, territory, or timing need a new review. Remove expired or withdrawn assets and stop use when the permission or agreement ends.
Before release, verify names, claims, rights, final artwork, clear space, sizes, accessible text, links, required disclosures, current availability, and written approvals. A design file, portal login, or past approval is not permission for a new use.
12 / SSO BRAND SYSTEM
Trademarks, permissions & legal use
Treat names and artwork as owned assets. When a campaign falls outside the permission already granted, ask before using it.
Preserve official names
Use SSO and third-party product names exactly as their owners specify, including capitalization, spacing, and any required notices. Keep brand names untranslated unless an owner-approved local form exists. Do not make a product trademark plural or possessive; use a phrase such as services, devices, or products instead.
Permission has limits
Use SSO marks, partner marks, service marks, product images, and supplied advertising only for the approved purpose, medium, territory, and period. A use outside these guidelines or your agreement requires prior written authorization from the owner. These guidelines do not transfer ownership or grant an unrestricted trademark license.
Respect other owners
SSO approval does not replace permission from another trademark owner, creator, photographer, or rights holder. Check each owner’s current requirements and the terms attached to the material. Do not imply that a third party sponsors or endorses SSO or your business without explicit authorization.
Keep legal details accurate
Use the public-facing company name in ordinary communications. Use the actual legal entity name in contracts and legal notices where required. Include trademark attributions and other disclosures when the relevant agreement or rights holder requires them; never add registration symbols or legal claims by assumption.
For questions about an SSO use, contact your SSO representative through the Partner Portal before publication. For another owner’s material, obtain that owner’s separate permission. Your signed agreement and any asset-specific restrictions continue to apply.
