PIES Studio 1.9 ยท Documentation
PIES Studio carries your brand in three places, each set separately:
| Where | What it changes | Who sets it |
|---|---|---|
| Platform branding | The Studio itself: sign-in page, sidebar logo, favicon, platform name, colour palette, and the layout of every e-mail Studio sends | An administrator, in Administration โ Branding |
| Application branding | One application: its icon, logo, mini logo, display name, version and splash colour, shown in the generated app and its previews | Anyone who can edit the application, in the application's Settings |
| Application theme | The look of the generated screens: colours, fonts, header and menu | The application's Themes and the Header Builder; see Themes |
Branding is cosmetic. Nothing you change here affects data, access or licences, and every change can be undone.
Open Administration, choose the Branding tab and press Edit. The page has four groups:
| Group | Fields | Notes |
|---|---|---|
| Platform identity | Platform name | Replaces "PIES Studio" in the sign-in page, the browser title and e-mails |
| Logos | Icon (light, dark), Full logo (light, dark), Favicon (light, dark) | PNG or JPEG for icons and logos, PNG or ICO for favicons. Light variants show on light backgrounds, dark variants on dark ones; a missing dark variant falls back to the light one |
| Colours | Primary and Secondary (light, dark), Primary button, Destructive button, Button gradient (start, end, angle), Primary font and Secondary font (light, dark) | Used by Studio's own screens and as the defaults for new application themes |
| no separate fields | Invitations, password resets and deployment e-mails use the platform name, the full logo and the primary colours above |
Press Save. Studio reloads its branding straight away; people already signed in see it on their next page load. The sign-in page reads the branding before anyone signs in, so the logo your users see first is yours.
Restore Defaults removes every custom value and returns Studio to the PIES look. This is the only way to clear a logo once uploaded.
| Asset | Shown in |
|---|---|
| Icon | Collapsed sidebar, browser tab in generated apps, share previews |
| Full logo | Sign-in page, expanded sidebar, e-mail header |
| Favicon | The Studio browser tab |
The assets are stored in Studio's own database, not fetched from the internet, so they work offline. The e-mail layout embeds the logo, so mail clients show it even when they cannot reach the server.
Open the application, choose Settings and scroll to the branding tiles:
| Field | Purpose | Format |
|---|---|---|
| Icon | Required. Favicon of the generated app, its home-screen icon on phones, and share previews | PNG or JPEG, square |
| Logo (wide) | The masthead of the generated app's header and sign-in page | PNG, JPEG or SVG, up to 2 MB |
| Mini logo | The compact mark used where a wide logo does not fit, such as a collapsed menu | PNG, JPEG or SVG, up to 2 MB, square |
| Display name | The name users see in the generated app. Leave empty to use the application's name | Text |
| Version | The version number recorded on the application and shown by generated apps that display one | 1.2 or 1.2.3 |
| Splash background | The colour recorded for the generated app's loading screen | Colour |
Logo and mini logo fall back to the icon when they are not set, so an application with only an icon is still fully branded. Remove on a tile clears that asset.
The generated application picks these up on its next build or preview; a running preview refreshes when you rebuild it.
Colours, fonts and the layout of the header and menu belong to the application's theme, not to branding. Change the theme and every screen follows. See Themes and the Header Builder in the Studio manual, and Quickstart for asking PIES AI to restyle an application in your brand colours.