Skip to main content
This is step 2 of the Base44 white label setup skill. Work through these parts in order. Use the API for each part, as the linked page documents it. Once white label is on, every app built or edited in the workspace follows these settings, from its next build turn. Tell the person that in one sentence before you turn it on. If a call is refused because the account isn’t a workspace owner or admin, guide the person, or an owner or admin, through that part in workspace settings instead: White label → Settings.

​
Set the brand

  • Read: Brand.
  • Ask: “What name should the AI use for your platform, should the assistant have its own name, and do you have brand colors, fonts, or a style guide the apps should follow?”
  • Default: The platform’s product name as the brand name, no separate agent name, and one design system from the person’s brand as the workspace default.
  • Do: With the white label settings endpoint, turn white label on and save the names in one PATCH, with enabled, brand_name, and agent_name if the person gave one. Then generate the design system, wait until it’s ready, set it as the default, and set use_default_design_system to true. Read the settings back with GET and confirm every field you sent applied. Don’t send agent_prompt or ask about the system prompt: setup keeps Base44’s prompt, unless the person asks to write their own.
  • Verify: In a new build, the agent uses the brand or agent name, never Base44, and the app uses the brand’s colors and fonts. If the design isn’t applied, check the design system conditions on the Brand page.
  • Skip when: Never skip the names. Skip the design system if the person has no brand guidance yet.
Turning it on means accepting the White Label Terms. Before you send enabled: true, link the person to the White Label Terms, tell them that turning on white label accepts these terms for their workspace, and wait for their yes. Don’t turn it on without it.
Turning it on needs a brand name. Send brand_name in the same request as enabled: true. If GET returns controls_visible set to false, or turning it on returns a 404, white label isn’t available for the workspace yet: stop this step, tell the person, and say they don’t need to change anything in their setup.

​
Add skills and integrations

  • Read: Skills and MCP.
  • Ask: “Are there conventions every app should follow, or platform tools and data the apps need to reach?”
  • Default: No skills or MCP servers until the person names a need.
  • Do: If the account is an owner or admin, create each skill with the API, with a description written as a trigger. Otherwise, guide the person through adding it in the app. Connect MCP servers in the app, signed in as the integration account.
  • Verify: A build that needs the skill or tool uses it. Check the transcript for the skill or tool call.
  • Skip when: The person has no conventions or tools to add yet.