Sapeans

Make the community feel unmistakably yours.

Shape community identity with logos, cover imagery, colors, fonts, navigation, favicon, custom domains, and plan-aware white-label controls.

Brand ownership needs both creative control and honest plan boundaries.

A community identity must work in a directory card, browser tab, mobile header, desktop navigation, installed window, and custom domain. Sapeans separates the square mark from the wider navigation wordmark and carries supported appearance choices through the community shell, while plan messaging explains when Sapeans identity remains visible.

What it makes possible

Use the right logo for the surface

The square logo represents the community in discovery, cards, notifications, and compact identity. A landscape logo serves the tenant navigation bar, with the square image retained as a compatible fallback.

Choose supported colors and fonts

Appearance settings define the community’s primary, accent, background, text, and supported font choices. Preview behavior follows the current responsive web implementation rather than inventing a separate app-only theme.

Shape the public presentation

Cover, banner, tagline, community images, favicon, and supported navigation settings establish the identity that members meet across public and signed-in surfaces.

Connect and verify a domain

Domain settings provide the current custom-domain entry and verification states. The connected host resolves into the same community-aware routing and access behavior.

Understand white-label behavior

Sapeans keeps Sapeans identity visible on a custom domain. The current Enterprise copy includes no visible Sapeans identity, white-label login and identity controls, and removal of Sapeans branding.

How it works

Establish identity

Upload the square and landscape logos and set the public visual foundation.

Shape appearance

Choose supported colors, fonts, cover imagery, favicon, and navigation settings.

Preview

Review the responsive community shell before saving the applicable appearance changes.

Connect the domain

Add and verify a custom domain when the current plan permits it.

Controls for community builders

Appearance settings

Eligible admins manage logos, imagery, colors, font, navigation, and other supported identity fields.

Domain states

Domain cards keep connection, verification, error, and plan-unavailable states visible.

Plan identity

The UI preserves the current distinction between Sapeans branding and Enterprise white-label behavior.

Plans, permissions, and availability

Sapeans currently supports enhanced appearance and a custom domain with Sapeans identity visible. Enterprise includes advanced identity, domain, branding, white-label login, and branding-removal behavior in current public copy.

Frequently asked questions

Why are there square and landscape logos?

The square logo works across cards and compact identity, while the landscape logo is designed for the primary tenant navigation bar.

Can Sapeans remove all Sapeans branding?

No. Current plan copy says Sapeans identity remains visible on Sapeans. Branding removal belongs to the Enterprise description.

Does a custom domain change the community’s access rules?

No. The host changes, but the community’s membership, authentication, routing, roles, and feature gates continue to apply.

Do mobile surfaces use a different brand?

Supported responsive, installed, and native surfaces derive community identity from the same saved branding contract, subject to current parity and platform support.