App Config

Configure identity, data, domains, branding, integrations, and app preferences.

App Config holds an app's settings — its identity, its database, its domains and branding, its environment variables and integrations, and developer and notification preferences. Open it with App Config in the workspace action bar.

App Config has eight sections: Basic Config, Database, Domains, Brand Guidelines, Environment Variables, Integrations, Developer Tools, and Preferences. Several settings distinguish the Preview build from the Published one — so check which scope you're editing.

Basic Config

Set the app's App Name (required — the app can't be saved without it) and its App Description, then Save. The name is how the app is identified across Console.

Basic Config.

Database

Choose the database the app uses. Qore offers Uptiq Managed DB — a managed PostgreSQL database — which shows as Connected when in use, with a ••• menu beside it, and Supabase (Postgres plus auth and APIs) as an alternative.

To connect the database and choose its schema when you publish, see Deploy › Connect the database.

Choosing the app's database.

The managed database is the simplest path — Qore runs it for you. Connect Supabase instead when you need its auth and API features.

Domains

Under Connected Domains, use Connect New Domain to attach a domain from a third-party provider, so the published app serves from your own domain rather than the default Qore URL.

Connecting a custom domain.

Brand Guidelines

Set the app's visual style and branding in Design and Branding Preferences. Three tabs set where the design comes from:

• Current app design — the design this app uses now.
• Choose from project designs — a saved design from the project.
• Create new project design — a new design.
• Visual Style — choose the design language: Auto (Recommended) lets Qore pick, or select one of Minimal, Modern SaaS, Neumorphism, Glassmorphism, Enterprise, Dark Mode, Bold & Colorful, or Fintech / Banking.
• Brand Logos — upload a Full Logo (headers and branding), a Small Logo (compact spaces), and a Favicon (browser-tab icon, best at 32×32 or 64×64 px).
• Brand colors — set the Primary Brand Color and Secondary Brand Color (for example, #2b7fff and #f4f4f5), with Advanced Customization for finer control.
• Advanced Customization — expand it to set Primary Foreground, Secondary Foreground, Background, Foreground, Border, Input, Muted, Muted Foreground, Accent, Accent Foreground, Sidebar, and Sidebar Foreground. Each takes a colour, as a swatch or a hex value. Select Hide Advanced Customization to collapse it.

Create new project design has the same fields.

Brand Guidelines.

Advanced Customization.

More Advanced Customization fields.

Use Apply to save, or Reset Changes to discard.

Environment Variables

Store the API keys, tokens, and credentials your app's integrations need. Values are encrypted and injected as environment variables at runtime. Add each as a Key and Value with + Add Variable, then select Save. A Preview / Publish toggle lets you set different values for the preview build and the published build.

Environment Variables.

Environment variables hold secrets. They're encrypted at rest and only injected at runtime, but treat the values as sensitive — set them here rather than hard-coding them into the app.

Integrations

Connect the app to outside tools and platforms. The catalog holds 73 connectors across categories such as Storage, Authentication, LLM, Payments, CRM, Accountancy, Email Notification, Messaging, and Banking — for example Airtable, Confluence, DocuSign, the Google Workspace apps, and the Microsoft 365 apps. Search or narrow by category, then Connect the ones you need.

The Integrations catalog.

Connecting an integration grants the app access to that service. Connect only what the app actually uses.

Developer Tools

Turn on Enable Developer Tools to inspect the app's runtime behavior in the preview — useful while debugging, off by default. Select Save to keep the change.

Developer Tools.

Preferences

Turn on Build Notifications to be notified when a project build completes, so you don't have to watch the workspace to know a build finished. Select Save to keep the change.

Preferences.

App Config sections

Element	Description	When to use it
Basic Config	The app's name and description	Rename the app or update its description; App Name is required
Database	The connected database (Uptiq Managed DB or Supabase)	Choose or switch the app's database
Domains	Custom domains for the published app	Serve the app from your own domain
Brand Guidelines	Visual style, logos, and brand colors	Set the app's look and branding
Environment Variables	Encrypted secrets injected at runtime	Store API keys and credentials; set per Preview/Publish
Integrations	The 73-connector catalog	Connect the tools the app uses
Developer Tools	Runtime inspection in the preview	Turn on while debugging
Preferences	Build-completion notifications	Get notified when a build finishes

Why this matters

• App Config is where an app's identity, data, connections, and look are all set.
• Several settings differ between the Preview and Published builds — confirm the scope before you change one.
• The database, domain, integration, and environment-variable sections grant access or hold secrets; treat them with more care than the cosmetic ones.

Related

App WorkspaceIntegrations Hub

---

Maintained by Abhishek Paul AI-assisted, human-approved