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.
Shape community identity with logos, cover imagery, colors, fonts, navigation, favicon, custom domains, and plan-aware white-label controls.
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.
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.
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.
Cover, banner, tagline, community images, favicon, and supported navigation settings establish the identity that members meet across public and signed-in surfaces.
Domain settings provide the current custom-domain entry and verification states. The connected host resolves into the same community-aware routing and access 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.
Upload the square and landscape logos and set the public visual foundation.
Choose supported colors, fonts, cover imagery, favicon, and navigation settings.
Review the responsive community shell before saving the applicable appearance changes.
Add and verify a custom domain when the current plan permits it.
Eligible admins manage logos, imagery, colors, font, navigation, and other supported identity fields.
Domain cards keep connection, verification, error, and plan-unavailable states visible.
The UI preserves the current distinction between Sapeans branding and Enterprise white-label behavior.
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.
The square logo works across cards and compact identity, while the landscape logo is designed for the primary tenant navigation bar.
No. Current plan copy says Sapeans identity remains visible on Sapeans. Branding removal belongs to the Enterprise description.
No. The host changes, but the community’s membership, authentication, routing, roles, and feature gates continue to apply.
Supported responsive, installed, and native surfaces derive community identity from the same saved branding contract, subject to current parity and platform support.