Skip to main content

​
App files vs project files

Ask whether a file is part of the app recipe (shared branding, custom screens) or project data (uploads, client documents). That choice decides export/import and who can see the file.
Store the company logo as an app file used across projects. Client invoices stay as project files, private to the uploader unless we share them with the project.
In the UI: App Blueprint → Files for app files, and Files under the selected project for project files. After export/import, app files travel with the blueprint; project uploads do not. Confirm portal My Files and page links match the access you expect. Project files are a shared workspace with file-level access:
  • New writes are private by default (form uploads, chat attachments, exports, generated files). To share a file with every authenticated member of the project, ask Build to mark that file as project-visible (for example a product image on a shared catalog page).
  • Private files stay with the owning end-user. Builders still see them in project Files for support. Each row shows ownership and access as icons (person = end-user file, folder = shared workspace; lock = private, unlocked = shared with the project), with a hover summary. Filters cover All / Shared workspace / End-user files.
  • End users see their own private files under portal My Files. They can open project-visible files from pages and chat when the app links to them.
When you open a custom screen file in App Blueprint → Files, the preview shows the name and which pages use it. Text and code files also have a Copy control in the preview.

​
Project branding overrides

App logos, public brand colors, and public brand fonts (under App Settings) are the default for every project. A project can override colors and logo without changing the app blueprint. If guests use dark mode, ask Building chat to add a logo for dark backgrounds so public intake keeps a readable mark.
  • Open Project Settings → Branding to upload a project logo or favicon, or set public brand colors.
  • After you replace an app favicon, Publish so guests see it. A project favicon override is live. Refresh the public page (or open a new tab) to load the new tab icon.
  • Clear a project override with Use app default to fall back to App Settings.
  • Clear app-level colors under App Settings → Appearance → Public brand colors with Use platform default to restore GenieForge blues.
  • Overrides apply on that project’s portal, public intake forms, slug pages, and emails. They are not included when you export or import the app.
  • Choose Body and Display fonts under App Settings → Appearance → Public brand fonts (curated list). They apply to portal, Preview, guest landings, and app pages. Arabic uses Tajawal unless you pick another Body font.
  • After you change app brand colors, Project Settings → Branding shows the new inherited default, and Preview → Draft on the landing shows them before Publish. Guests keep the last published colors until you Publish.

​
Analyze a photo

A camera or upload on a page can analyze a project image without sending the person through chat. Build stores the photo as a project file, then asks a chat model you pick to read it (foods on a plate, a receipt, a product label). You always choose the model. iPhone camera photos (HEIC) are converted automatically. Attachments in native chat still work the same way. HIPAA-mode apps can analyze photos with an allowed Bedrock model. Generating new images stays off in HIPAA mode.