Base44 Release Notes

Designing your app

Browse the component library in your app editor to add polished, ready-made UI components that Base44 rebuilds to match your app’s theme, fonts, and content.

The component library is a collection of polished, ready-made UI components that you can add to your app straight from the AI chat in your app editor. Instead of describing a layout from scratch, you browse curated components, pick the one you want, and Base44 rebuilds it inside your app.

Tip

When you add a component, Base44 themes it to match your site, adapting its colors, fonts, and content to fit your app rather than dropping in a generic block. You can always customize the design further by asking the AI chat.

The component library in your app editor

Opening the component library

You open the component library from the plus menu in your AI chat, next to where you type your prompts.

Tip

When you select a component, the AI chat switches to Build mode automatically. For more on chat modes, see AI chat modes.

To open the component library:

• Go to your app editor.
• In the AI chat, click the plus icon next to the prompt box.
• Click Explore component library.

Opening the component library from the plus menu

Browsing and previewing components

The component library opens in a large window, with a search box at the top and a list of categories on the left. All components shows everything in the library, and each category groups components by purpose, such as Commerce, Navigation, and Booking & Scheduling.

You have 3 ways to find a component:

• Search: Type a keyword in the search box. It searches the category you have open, so choose All components first to search the whole library.
• Categories: Click a category on the left to see only its components. On a phone, the categories appear as a row above the search box.
• Filters: Click Filters to narrow the list by tag.

Hover over a component to see it in action, then click it to open its details. You see a live preview that you can switch between Desktop and Mobile, a short description, and for some components, Try different states to see each state before you add it. Use the arrows next to the component’s name to move to the previous or next one.

Browsing a category in the component library

Adding a component

From a component’s details, you tell the AI how to use it, then add it to your prompt or build it right away. You add one component per message. When you send the message, Base44 rebuilds the component as React code inside your app and adapts its styling, fonts, and copy to match your design.

To add a component to your app:

• Click the plus icon next to the prompt box in the AI chat in your app editor.
• Click Explore component library.
• Click the component you want.
• Under How should the AI use it?, describe where it goes, such as a page or section. This step is optional.
• Click Add to chat to place it in your prompt so you can edit the message first, or click Build now to send it right away.

A component’s details, with Add to chat and Build now

Note

More about adding components:

• Quick add: To add a component without opening its details, click the + on its card.
• Looking again: To see a component again later, click its chip in the prompt box or above the message you sent.
• New code libraries: If a component relies on a code library your app doesn’t have yet, Base44 asks you to approve installing it as part of building the component. Learn more about adding and using npm packages.

FAQs

Click a question below to learn more.

Can I add more than one component at a time?

Does adding a component cost extra credits?

Can I change a component after adding it?

Original source

Selling on your app

Track your app’s sales on the Payments tab. Compare revenue across time periods, review every transaction, and see which customers are on your recurring plans.

Track your app’s sales from your app dashboard. Compare revenue across periods, review every payment, and see which customers are on a recurring plan.

The Payments tab in your app dashboard

Tip: The Payments tab appears once you connect a payment provider. See Setting up Base44 Payments or Setting up Stripe.

Viewing your payments

Your payment data is grouped into tabs: Overview for your totals and revenue trend, Transactions for every individual payment, and Subscriptions when your app sells recurring plans.

Overview

The Overview tab summarizes how your app is selling over a period you choose.

To view your payment overview:

• Go to your app dashboard.
• Click Payments.
• Under Payment activity, click 7 days, 30 days, or 90 days.

Base44 shows 30 days by default. The tab shows:

• Net revenue: Your total for the selected period, with the change against the previous period and a chart of the trend, calculated net of refunds.
• Transactions: A count for the period, with a breakdown of how many succeeded, were refunded, and failed.
• Active subscriptions: A count of the customers currently on a plan.
• Recent transactions: Your latest 5, with View all to open your full list.

Note: When your app takes payments in more than one currency, a Currency picker appears on the Overview tab. Use it to choose which currency to report, so your net revenue and your chart always show a single currency.

Transactions

The Transactions tab lists every transaction for your app, with the newest first.

To view your transactions:

• Go to your app dashboard.
• Click Payments.
• Click Transactions.

Each row shows the Customer, Amount, Status, and Date. Scroll the list to load more transactions.

The Transactions tab, listing every payment and its status

A transaction has one of these statuses:

• Succeeded: The payment went through.
• Refunded: The amount was returned to the customer.
• Failed: The payment was reversed after a dispute.

Subscriptions

Your app can sell recurring plans through either Base44 Payments or Stripe. Ask the AI chat to add subscriptions to get started. The Subscriptions tab appears once your app sells plans through Base44 Payments.

To view your subscriptions:

• Go to your app dashboard.
• Click Payments.
• Click Subscriptions.

The tab lists the plans your customers are on, with Active subscriptions and Total subscriptions counts at the top. Each row shows the Plan and its billing cycle, Customer, Amount, Status, and Next charge date.

The Subscriptions tab, listing your recurring plans

A subscription has one of these statuses:

• Active: Billing on schedule.
• Canceling: The plan stays active until the end of the current period, then stops renewing.
• Past due: A payment failed and the plan is at risk.
• Canceled: The plan has stopped.
• Paused: Billing is on hold.

Note: View and manage subscriptions sold through Stripe in your Stripe dashboard. See Setting up payment flows.

FAQs

Click a question below to learn more about tracking your payments.

Where does the payment data come from?

Why is my net revenue different from the total of my transactions?

How do I refund a customer or handle a dispute?

Why don't I see the Payments tab in my native app?

Original source

Create a workspace design system in Base44 to define your brand’s colors, fonts, logo, and components once, then apply one consistent look across your apps.

A design system saves your brand’s look and feel at the workspace level: its colors, fonts, logo, and a set of matching components. Create it once, set it as your default, and every new app you build starts on-brand, so you do not have to redefine your style each time.

You do not need to be a designer. With just a few details, such as your logo, a short description of your brand, the feel you want, and any design files you have, Base44 creates an entire design system for you, so all your apps look professional and on brand.

Availability

• Design systems are available on the Builder plan and above. Each workspace can have 1 design system, and as many as you need on the Enterprise plan.
• Design systems apply to web apps, not to mobile apps. An app imported from Figma, started from a URL, or migrated from another platform can take a design system once it has finished building.
• Creating and using a design system does not cost credits.

What’s included

When you create a design system, Base44 fills in everything that keeps your apps looking consistent and on brand, and shows it all in a live preview. Change a color or a font, and every example updates right away, so you always see how it looks.

A design system covers 3 things:

• Your brand basics: Your logo, brand name, tagline, and a short description, plus your brand’s core values, tone of voice, and design guidelines for how it should look.
• Your look and feel: Your colors, your fonts, how rounded your corners are, how much shadow sits under things, and how much space goes between them.
• Ready-made pieces: A complete set of components that already match your brand and are ready to drop into any app, including buttons, icons, cards, navigation, forms, and page sections, each styled for its interactive states.

Creating a design system

Workspace owners and admins create design systems from the workspace settings. In one form you can combine a short description, your logo, an import from Figma, a website, or an npm package, and your own design files, and Base44 generates a complete design system from whatever you provide.

To create a design system:

1. Click your workspace name at the bottom left, then click Settings.
2. Click Design system.
3. Click Create. If your workspace already has a design system, click Create new design system instead.
4. In Create your design system, add any of the following:
   • Describe your brand: Write a short description of your brand, and add your logo in the square beside it.
   • Import an existing source: You can use one source per design system. Switch between the tabs:
     • Figma file: Drop or browse a .fig file, up to 1.9 GB, and attach all of its pages and frames or choose specific ones. Base44 downscales oversized images and prepares large files in the background, and does not store the original file.
     • Website URL: Paste a website address. Only use URLs where you have the rights to the content.
     • NPM package: Enter a published package by name, name@version, or an npmjs.com link. It resolves from the public npm registry by default, or click Private registry to add a registry URL, an access token, and any scopes that should resolve there. Your access token is used once to fetch the package and is not stored.
   • Upload your design resources: Add images, fonts, a design.md file, or other design files, up to 10 files.
5. Click Create. Generating your design system can take a few minutes, and you can leave and come back while it runs.
6. Review the generated design system in the preview, then adjust anything you want.

Editing your design system

When you open a design system, you edit it in a two-panel editor. On the left are all of your brand and design settings. On the right, a live Preview shows those styles applied to real buttons, icons, and cards, the way they look in your app or website. As you change a setting on the left, the preview updates instantly.

Your design system’s name and tagline sit at the top of the page. Click either one to edit it in place.

On the left, you can edit each part of your design system:

• Overview
• Logos
• Typography
• Color palette
• Tone of voice
• Core values
• Corner radius
• Spacing scale
• Shadow
• Design guidelines

Your edits are not applied until you save them. Click Save changes to keep them, or Reset changes to undo edits you have not saved yet. A design system needs a name and an overview before you can save it.

Managing your design systems

Manage a design system from its card in the Design system section. Open the More actions icon on a design system to edit it, set it as your default, or delete it.

Who can manage design systems:

• Workspace owners and admins: Can create, edit, set the default, and delete any design system.
• Other workspace members: Can view design systems and attach one in the AI chat, but can’t create, edit, or delete them.

Setting a default design system

Set a design system as your workspace default so new apps start with it automatically.

To set your default design system:

1. Click your workspace name at the bottom left, then click Settings.
2. Click Design system.
3. On the design system you want, click the More actions icon and click Set as default.

To stop using a design system as your default, open the same menu and click Remove default.

Deleting a design system

Delete a design system you no longer need.

Deleting a design system from its card takes effect immediately, and it cannot be undone.

To delete a design system:

1. Click your workspace name at the bottom left, then click Settings.
2. Click Design system.
3. On the design system you want, click the More actions icon and click Delete.

Using your design system when building

When you start a new app, your default design system is preselected, so the app is built to match your brand from the first prompt. To choose a different design system, click the Add icon in the AI chat, select Use a design system, then pick the one you want.

You can also apply a design system to an app you are already working on, from the same Add icon in the AI chat. When your workspace has one design system, the option shows its name, and clicking it attaches the design system to your next prompt.

Applying a design system takes effect on a build turn in the AI chat. If your chat is set to a non-building mode such as Discuss, switch to Build first.

Applying a design system to an app that is already built rebuilds the app to match, rather than restyling it in place. Apply it early, or expect the app to be regenerated.

FAQs

Click a question below to learn more about design systems.

• Do I need design skills to create a design system?
• Can each client or project have its own design system?

Original source

Design branded emails for your Base44 app, preview them on any screen, customize built-in emails like password resets, and send them from your app’s workflows.

Design the emails your app sends so they look like your app, not a plain text message. From Emails in your dashboard, you can start from a ready-made template in your brand colors and fonts, ask the AI to design a new one, preview it on desktop, tablet, and mobile, and send yourself a test before your app users see it.

You can also customize the built-in emails Base44 sends your app users, such as password resets, and use any of your designed emails as a step in a workflow.

Note

If you are on the Free or Starter plan, you can preview and test the built-in emails, but designing your own emails and customizing the built-in ones needs the Builder plan or higher.

Starting from a template

Base44 writes a set of starter emails for each app, already styled with your app’s logo, colors, and fonts. Pick one to save it as your own email. It opens in the preview, ready to change as much as you like.

To start from a template:

1. Click Dashboard in your app editor.
2. Click Emails.
3. Under Start from a template, find the template you want. If your app has more than 3 templates, use the arrows to see the rest.
4. Hover over the template and click Use this template.

Designing with AI chat

Describe the email you want in the AI chat, and it designs the email for you in your app’s style. For example, Design a welcome email that thanks new members and links to their profile page. You can type it straight into the AI chat, or start from the Emails tab.

To design an email with the AI chat:

1. Click Dashboard in your app editor.
2. Click Emails.
3. Click Generate with AI.
4. Describe the email in the AI chat and send your message.

Previewing and testing

Open any email to see exactly what your app users receive, check how it looks on different screens, and send yourself a test copy.

To preview and test an email:

1. Click Dashboard in your app editor.
2. Click Emails.
3. Click the email you want to open.
4. Choose what you want to do:
   • Check other screen sizes: Click Desktop, Tablet, or Mobile above the preview.
   • Send a test: Click Send test to me to get a copy in your own inbox.
   • Change the email: Click Edit with AI and describe what to change in the AI chat.
   • Delete the email: For emails you designed, click Delete, then click Delete template to confirm.

Warning

Deleting an email cannot be undone. Any workflow or backend function that sends it stops working until you create the email again.

Customizing built-in emails

If your app has a login, it automatically sends 4 account emails to the people who use it. You don’t need to set them up or turn them on. Base44 sends them as part of your app’s signup and login, already styled with your app’s logo and colors.

• Password reset: Sent when a user asks to reset their password.
• Email verification: Sent when a user needs to verify their email address.
• User invitation: Sent when someone is invited to join the app.
• Access approved: Sent when an app access request is approved.

Changing them is optional. If you edit one, your version is sent instead of the Base44 one, and it shows Edited by you in the list. To go back to the Base44 version at any time, open the email, click Reset to default, then click Reset. This deletes your version and cannot be undone. Keep the link or button each email needs, such as the reset link, or your app users get the Base44 version. If your app uses its own login pages, you only see the emails Base44 still sends for it.

To customize a built-in email:

1. Click Dashboard in your app editor.
2. Click Emails.
3. Under Application emails, click the email you want to change.
4. Click Edit with AI and describe what to change in the AI chat.

Note

The email verification email goes to people who are still signing up, so your version has a few extra checks before it sends. Your app needs its own custom email domain, your version must show the verification code, and it is reviewed first, which can take up to an hour. Until then, your app users get the Base44 version, and the preview shows why under Sending.

Sending from workflows

Any email you design can be a step in a workflow, so it sends automatically when something happens in your app, such as a new signup or a completed order.

To add one, ask the AI chat, for example When a new user signs up, send them a welcome email. The AI designs the email and adds it to the workflow as a Send email step, ready to run. When you open the workflow, the step shows who the email goes to, its subject, and which template it uses.

Learn more about creating workflows, and about who your app can email.

Original source

Let people sign in to your app with Google Workspace, Microsoft, GitHub, Okta, or another OIDC provider. Set up your redirect URI and provider, then test SSO.

Step 1 | Get started with SSO

Single Sign-On (SSO) lets people sign in to your Base44 app using an external identity provider that supports OpenID Connect (OIDC), such as Google, Microsoft, GitHub, Okta, Apple, or Kakao, instead of creating a separate login for your app.

Notes:

• Single sign-on (SSO) for apps is available on an Enterprise plan (Business or Enterprise). Workspaces created before October 1, 2026 keep their earlier plan requirement, the Elite plan or higher.
• To connect a provider such as Kakao through SSO, you need your own account with that provider and an app configured there. You are responsible for creating and managing the client ID, client secret, redirect URI, and any other credentials in your identity provider’s dashboard.

To find your Base44 app ID and redirect URI:

1. Go to your app editor in Base44.
2. Check your browser’s address bar and find the app ID between /apps/ and /editor/ in the URL.
3. Build your redirect URI by replacing {{APP_ID}} in this format with your app ID: https://app.base44.com/api/apps/{{APP_ID}}/auth/sso/callback

Once you choose a provider, Base44 lists every callback URL for your app so you can copy them.

About callback URLs:

• Register every URL Base44 lists with your identity provider as an allowed redirect URI. Some providers, such as ClassLink, reject a login when the redirect URI does not exactly match a registered value.
• By default, an SSO login runs through app.base44.com even when your app has a custom domain. To keep it on your own domain, turn on Use this app’s custom domain as the SSO callback. This is off by default, and you need a verified custom domain on the Domains tab before you can turn it on. When you do turn it on, register the custom-domain callback URL with your provider as well.
• Most providers, including Google, Microsoft, and Okta, work with the default. Turn the custom domain callback on for providers that require the redirect URI to match your domain, such as ClassLink, Clever, and strict Azure or Entra policies.
• If your app uses your workspace SSO provider instead of its own, Base44 shows a workspace app login callback URL. Ask your workspace admin to add that URL to the workspace identity provider. Learn more about enforcing SSO across all workspace apps.

Step 2 | Choose your provider

Start by choosing the identity provider your team already uses. You can pick a built-in option (Google, Microsoft, GitHub, or Okta), or use Advanced / Manual configuration to connect any OIDC provider, including Kakao, or your own IdP.

Google Workspace

Use Google Workspace as your SSO provider with an OAuth 2.0 Web application. First, create an OAuth 2.0 client in Google Cloud Console for your project, then add those credentials in Base44.

Before you set up SSO, you’ll need:

• A client ID and client secret from Google Cloud
• Your app’s redirect URI (see Step 1)

To set up Google Workspace SSO in Base44:

1. In your app editor, click Dashboard.
2. Click Settings.
3. Click Authentication.
4. Click Set Up next to Single sign-on (SSO).
5. In Select SSO provider, choose Google Workspace.
6. Enter your Client ID and Client Secret from Google.
7. Keep Scope as openid email profile.
8. Leave Discovery URL set to the default value.
9. Click Enable SSO.

Microsoft

Use Microsoft Entra ID (Azure AD) as your SSO provider through your Azure portal.

Base44 supports both single-tenant and multi-tenant Microsoft configurations. What you enter in the Tenant ID field controls which accounts can log in.

Before you set up SSO, you’ll need:

• Application (client) ID and client secret from Azure
• Your app’s redirect URI (see Step 1)
• User.Read and standard OpenID Connect permissions (openid, email, profile) granted in your Azure app registration

To set up Microsoft SSO in Base44:

1. In your app editor, click Dashboard.
2. Click Settings.
3. Click Authentication.
4. Click Set Up next to Single sign-on (SSO).
5. In Select SSO provider, choose Microsoft Azure AD.
6. Enter your Azure Client ID (Application (client) ID) and Client Secret.
7. In the Tenant ID field, enter a value based on which accounts you want to allow:
   • Your directory (tenant) ID from Azure: Only people from your specific organization.
   • common: Personal Microsoft accounts and work/school (Microsoft 365) accounts.
   • organizations: Work and school accounts only (Microsoft 365).
8. Keep Scope as openid email profile.
9. The Discovery URL fills in automatically based on the tenant ID you entered. Confirm it looks correct before continuing.
10. Click Enable SSO.

GitHub

Use a GitHub OAuth app as your SSO provider. Create an OAuth app in GitHub Developer Settings, then connect it in Base44.

Before you set up SSO, you need:

• A GitHub OAuth app created in GitHub Developer Settings
• The app’s authorization callback URL set to your redirect URI (see Step 1)
• Client ID and client secret generated by GitHub for your OAuth app

To set up GitHub SSO in Base44:

1. In your app editor, click Dashboard.
2. Click Settings.
3. Click Authentication.
4. Click Set Up next to Single sign-on (SSO).
5. In Select SSO provider, choose GitHub.
6. Enter your GitHub Client ID and Client Secret.
7. Keep Scope as user:email.
8. Keep the default Auth Endpoint, Token Endpoint, and Userinfo Endpoint values for GitHub.
9. Click Enable SSO.

Okta

Use Okta as your SSO provider. In your Okta Admin Console, create an OIDC Web application for your Base44 app, then add the credentials in Base44.

Before you set up SSO, you’ll need:

• Okta client ID and client secret
• Your Okta subdomain (the part before .okta.com, for example your-company)

To set up Okta SSO in Base44:

1. In your app editor, click Dashboard.
2. Click Settings.
3. Click Authentication.
4. Click Set Up next to Single sign-on (SSO).
5. In Select SSO provider, choose Okta.
6. Enter the following:
   • Client Id: Your Okta client ID.
   • Client Secret: Your Okta client secret.
   • Okta Domain: Enter this in whichever form matches your Okta org:
     • Your Okta subdomain, for example your-company.
     • Your full custom Okta URL domain, for example login.your-company.com.
     • The issuer URL including the authorization server path, for example https://login.your-company.com/oauth2/default, if your Okta org uses API Access Management with custom authorization servers.
   • Scope: Keep openid email profile.
   • Discovery URL: This is generated from your Okta domain and marked Auto. You can edit it if you need to point Base44 somewhere else, and it then shows as Modified. To go back to the generated value, click Reset to auto.
7. Click Enable SSO.

Warning:

For some Okta orgs the default authorization server does not return the email claim Base44 needs, and sign-in fails with Email not returned by OAuth provider. To fix this, include the authorization server path in Okta Domain, for example https://your-domain.okta.com/oauth2/default. The Discovery URL picks that path up automatically, and you can also edit the Discovery URL directly. If your org does not have a custom authorization server, that address returns a 404, so use your plain Okta domain and map the email claim in your Okta app profile instead.

Advanced / Manual configuration

Use Advanced / Manual configuration to connect any OIDC compatible identity provider that is not covered by the built in options. This includes providers such as Kakao, as long as they support OIDC and you configure them with the correct details from your provider.

Before you set up SSO, you need:

• OIDC client credentials from your provider
• Your app’s redirect URI (see Step 1)
• Discovery URL or all OIDC endpoints from your provider
• Required scopes (openid email profile or equivalent)

To set up Advanced / Manual configuration in Base44:

1. In your app editor, click Dashboard.
2. Click Settings.
3. Click Authentication.
4. Click Set Up next to Single sign-on (SSO).
5. In Select SSO provider, choose Advanced / Manual Configuration.
6. Fill in the following fields using your provider’s values:
   • Name: A name for this SSO configuration (for example, Auth0, Keycloak, Kakao, or your identity provider name).
   • Client Id: Your OIDC client ID.
   • Client Secret: Your OIDC client secret.
   • Scope: Keep openid email profile.
   • Discovery URL: Your provider’s discovery URL, if available.
   • Auth Endpoint, Token Endpoint, Userinfo Endpoint, Jwks Uri: If you are not using a discovery URL, paste each endpoint from your provider’s documentation.
7. Click Enable SSO.

Use PKCE and Request offline access are on by default and appear only when you choose Advanced / Manual Configuration. Leave them on unless your provider rejects them.

• Use PKCE (recommended): Adds the standard OAuth 2.1 PKCE challenge to login. Turn it off only for providers that reject unknown OAuth parameters, such as ClassLink or older Shibboleth and ADFS deployments.
• Request offline access: Asks your provider for a refresh token. Turn it off only for providers that reject it, such as the ones above. It has no effect for providers that use response_mode=form_post, such as Apple.

Step 3 | Test your SSO login

After setting up SSO, test that everything works as expected.

To test your SSO login:

1. Log out of your app if you are currently signed in.
2. Go to your app’s login screen.
3. Click Log in with SSO or select the provider you configured.
4. Sign in using an email address from your approved domain.

You’ll be logged in automatically.

Automatically giving access to your app

Give people access to your app as soon as they sign in through SSO, with no invite. Auto-admit is a per-app setting that overrides your workspace default. It is off by default.

Before you begin: Auto-admit works only when the app is Private, SSO is its only sign-in method, and the person signs in through the SSO provider the app uses.

To set the workspace default for all private SSO-only apps, see automatically giving access to private apps.

To automatically give access to your app:

1. Go to your app’s Dashboard.
2. Click Settings.
3. Click Authentication.
4. Next to your SSO provider, click Configure.
5. Click the Auto-admit SSO users toggle.
6. Click Save SSO Settings, or Enable SSO if the app uses your workspace SSO provider.

Notes:

• Turning off auto-admit stops new people being admitted. It does not remove anyone who already has access. To stop someone signing in again, remove or suspend them in your identity provider.
• If your workspace enforces SSO for all apps, Auto-admit SSO users takes effect immediately. If the setting is disabled, check that the app is private and that SSO is the only enabled sign-in method.

FAQs

Click a question to learn more about SSO.

Original source

Opening the hub

You can open the hub from anywhere in your workspace.
To open the Workspace Hub:

1. Make sure you’re in the right workspace. Click your workspace name at the bottom left of your account to switch.
2. In the left sidebar, click Workspace hub.

Tip: Your workspace home page also shows a preview of the hub with your recent apps. Click Go to Hub to open the full hub.

What’s in the hub

The hub brings your workspace’s apps together in one page:

• Cover and description: A banner image and a short description that tell everyone what the hub is for.
• Stats: How many apps the workspace has, how many people used an app this week, and how many are using apps right now.
• Featured by your admin: The top section of the hub. It shows the apps your admins picked, or the most popular apps if nobody has picked any.
• Custom sections: Groups of apps your admins created, for example by team or workflow.
• Browse everything in your workspace: Every app in the workspace, with a search bar and filters for All, Your recently used, Most popular, and New this week.

On each app card, you can open the app, click Pin this app just for you to keep it handy, Copy app link, or Like this app.

Note: The Browse everything in your workspace area and the hub’s stats include published apps that are visible to the whole workspace. To add an app, set its visibility to Workspace. Learn more about setting your app visibility.

Setting up the hub

Workspace owners and admins can customize the hub. Until it’s fully set up, admins see a Finish setting up your hub card at the top with 4 steps: adding a cover image, writing a description, choosing featured apps, and creating a section. Only admins see this card.
You can add any published app in your workspace to Featured or a section, whatever its visibility. Each member only sees the apps they have access to, so a private app appears only for the people who can open it. When you choose apps, private ones are marked so you can tell them apart.

Tip:

Before you begin:

• You need to be a workspace owner or admin.
• Your changes are saved as a draft until you click Save changes. Members see them after you save.

Adding a cover image

A cover image gives your hub a visual identity. It appears at the top of the hub for everyone.
To add a cover image:

1. Click Workspace hub in the left sidebar of your workspace.
2. Click Edit hub.
3. Click Add cover photo and choose an image.
4. Drag the image to position it, and use the zoom slider to resize it.
5. Click Save changes.

Writing a description

A short description tells people what the hub is for.
To write a description:

1. Click Workspace hub in the left sidebar of your workspace.
2. Click Edit hub.
3. In Workspace description (optional), enter up to 200 characters.
4. Click Save changes.

Choosing featured apps

Featured is always the top section of your hub. It shows the most popular apps by default, but you can choose the ones you want.
To choose featured apps:

1. Click Workspace hub in the left sidebar of your workspace.
2. Click Edit hub.
3. In the Featured section, click Add apps.
4. In Add apps to this section, select the apps you want to feature. Use the search bar or the sort menu to find them.
5. Click Save.
6. Click Save changes.

Adding sections

Sections group apps by team, workflow, or any other category, so people can find what they need.

Note:

How sections work:

• Members don’t see a section until it has at least one app.
• To reorder or delete a section, click the Section actions icon next to it and select Move up, Move down, or Remove section.

To add a section:

1. Click Workspace hub in the left sidebar of your workspace.
2. Click Edit hub.
3. Click Add section.
4. Click Name this section and enter a name.
5. Click Add apps, select the apps for this section, and click Save.
6. Click Save changes.

Adding a logo

Add your organization’s logo and rename the hub so it feels like your own.
To add a logo or rename the hub:

1. Click Workspace hub in the left sidebar of your workspace.
2. Click Edit hub.
3. Do one of the following:
   • Click Add workspace logo to upload a PNG, JPEG, WEBP, or GIF image.
   • Click Rename hub, enter a new name, and click Save name.
4. Click Save changes.

Original source

SEO and GEO

Scan your app on the SEO and GEO page, read your score, and fix issues. Track AI visibility, edit meta tags, and choose which pages appear in search results.

SEO and GEO can feel overwhelming, but Base44 takes care of the technical foundation for you. The SEO & GEO page in your app dashboard lets you manage your app’s visibility in search engines and AI-powered search platforms like ChatGPT and Gemini.

Improving your score is easy, because Base44 guides you through every step. Run a scan to see how your app is doing, then let the AI fix most of the issues for you with a single click. For the few that need your input, Base44 shows you exactly what to do to raise your score.

The page has an Overview tab, an AI Visibility tab, a Meta tags tab, and an Advanced settings tab. Run a scan to get a score and a prioritized checklist of improvements, see which AI assistants are reading your pages, set custom meta tags for each page, and control settings like indexing and structured data injection.

Overview

The Overview tab is your main SEO control panel. It contains your setup checklist and, once you connect it, your Google Search Console data. Run a scan to see how your app scores, fix the issues it finds, and manage the SEO files and features Base44 generates for you.

Running a scan

The SEO & GEO scan checks your app against a full list of SEO and GEO criteria and gives you a prioritized checklist of issues to fix. Your score reflects how well your app is set up for search engines and AI-powered search platforms.

Tip

Before you begin: Publish your app. Search engines and AI tools can only find a published app, so until you publish, your score cannot rise above a certain point no matter what else you improve. Click Publish in your app editor, then run a scan.

To run a scan:

1. Click Dashboard in your app editor.
2. Click SEO & GEO under Marketing.
3. Click Run scan.

Reading your score and checklist

After the scan, Your SEO score shows a rating of Low, Moderate, or High, with a checklist of everything the scan found. Click any item to expand it and see what it means and what you can do about it.

Use the filters above the checklist to focus on what matters most:

• All: Every item in the checklist.
• Urgent: Issues that are directly hurting your visibility and should be fixed first.
• Recommended: Improvements that can boost your score but are not blocking your current performance.
• Done: Checks your app has already passed.

Fixing issues

After running a scan, you can fix issues one at a time or send everything to the AI chat at once.

Tip

Once the changes are made, click Scan again to see your updated score.

Connecting Google Search Console

When you connect your app to Google Search Console, your clicks, top searches, and indexing show up right on the Overview tab. Base44 verifies your site and submits your sitemap for you. To learn how to connect it, fix verification problems, and read your data, see Connecting Google Search Console.

Warning

Connecting your app to Google Search Console is rolling out gradually.

AI Visibility

When someone asks an AI assistant a question your app can answer, the assistant opens one of your pages to read it. The AI Visibility tab shows you which pages get read, which assistants read them, and how many of those people then clicked through to your app.

Warning

AI Visibility is available on the Pro plan and above.

Everything on this tab covers the last 7 days, and your activity is kept for 60 days. If you have just published, you may see No AI reads yet. It can take a while for AI assistants to find a new app.

Tip

Before you begin: Turn on AI assistant discovery on the Overview tab. It is the setting that helps assistants find and understand your pages, and this tab shows you what they read once they do.

To open AI Visibility:

1. Go to your app’s dashboard.
2. Click Marketing in the left menu.
3. Click SEO & GEO.
4. Click the AI Visibility tab.

Summary cards

4 cards across the top give you the shape of your AI traffic at a glance. Your app in AI answers also shows the change against last week when it rises.

Pages AI read to answer someone

This list shows one row per page and assistant, with how many times that page was read. It is the detail behind the Your app in AI answers card, so you can see exactly which content is doing the work.

Base44 recognizes ChatGPT, Claude, Perplexity, Gemini, and Meta AI.

Topics in this list are guessed from the page the assistant opened. Assistants never share what the person actually typed, so Base44 cannot show you the question behind a read.

Where AI sends people

The cards tell you that AI is reading your app. This section tells you whether any of it turns into visitors. It appears once an assistant has actually sent you someone, so if Visits from AI is still 0, you don’t see it yet.

It lists the assistants that sent you real people, how many visits came from each, and the page each one lands on most. An assistant that reads a lot but sends nobody is a sign your content is answering the question so completely that there is no reason to click, which may be fine or may mean the page needs a clearer reason to visit.

Referrals are recognized from ChatGPT, Claude, Perplexity, Gemini, Meta AI, Copilot, DeepSeek, Grok, and Mistral.

Meta tags

Meta tags are hidden snippets of text in your page code. Search engines read them to understand what each page is about. They control the title and description shown in Google search results, and what appears when someone shares a link to your app on social media. Setting clear, accurate meta tags for each page can improve your click-through rate in search results.

The Meta tags tab is where you set those tags and choose which pages are allowed to appear in search at all.

Letting Base44 write your tags

Automatic titles and descriptions lets Base44 add a standard title, description, and preferred URL to every page. Leave it on unless you already set these tags yourself in your app’s code, in which case turn it off so Base44 does not add its own alongside yours.

Note

Meta tags set here are enforced by the platform and take priority over any title tags in your app’s code. If the title shown in search results or when sharing a link doesn’t match what’s in your code, check this tab. A saved meta tag here may be overriding it.

Editing a page’s meta tags

Page search settings lists every page in your app, with its title and description.

To edit a page’s meta tags:

1. Click Dashboard in your app editor.
2. Click SEO & GEO under Marketing.
3. Click the Meta tags tab.
4. Click the Edit icon next to the page you want to update.
5. Update the Title and Description fields.

• Title: Aim for 10 to 60 characters.
• Description: Aim for up to 160 characters.

1. Click the Save icon to confirm.

Note

If a page shows an orange warning, a previously saved override is active and taking priority over your App Overview values. Click the Trash icon next to that page to clear it and restore your current App Overview values.

Choosing which pages appear in search

Indexing is how search engines read your pages and add them to their database so they can appear in search results. If a page is not indexed, it doesn’t show up in search results or AI recommendations.

Each row in Page search settings has a Search visibility toggle, and every page starts switched on. Turn a page off to keep it out of search: Base44 removes it from your sitemap and llms.txt file, and adds a noindex tag to it.

Note

If your app is open to everyone and you have put individual pages behind a login, Base44 keeps those pages out of search for you. If your whole app requires a login, it does not, so use these toggles to choose what appears in search.

Advanced settings

The Advanced settings tab controls the files and extra data Base44 creates for search engines and AI tools.

AI assistant discovery

When someone uses an AI assistant such as ChatGPT, Gemini, or Perplexity to find or compare tools, those platforms scan the web and use structured signals to decide what to surface. Base44 generates an llms.txt file for your app, a lightweight file that gives AI crawlers a clear, structured summary of what your app does. This helps your app be understood and recommended by AI-powered search tools.

Turn AI assistant discovery on or off to control whether Base44 generates this file.

Search engine files

These are the standard files that help search engines crawl and index your app. Turn one off only if you serve your own version of that file.

• Robots.txt file: Tells search engines and AI crawlers which parts of your app they are allowed to visit. When it is on, Base44 generates the file for you. When it is off, Base44 serves your deployed public/robots.txt if it exists, or returns a 404.
• Sitemap: Lists your app’s pages so search engines can find and index them faster. When it is on, Base44 generates the file for you. When it is off, Base44 serves your deployed public/sitemap.xml if it exists, or returns a 404.

Structured data

Structured data is hidden code in your page that gives search engines extra context about your app, such as your brand details, page structure, and FAQs. Search engines use it to show richer results, like FAQ dropdowns or brand information.

• Structured data: Adds details about your app, your business, and your FAQs. Turn it off if you provide your own structured data, so Base44 does not add its own alongside it.
• Breadcrumbs: Creates the trail of links shown on a page, such as Home > Products > Item, so search engines understand where a page sits in your app. Turn it off to serve your own breadcrumb structure as it is.

FAQs

Click a question below to learn more.

Original source

Work on your codebase in Base Code. Connect GitHub, choose a repository, make changes with the AI chat, open pull requests, and manage branches and secrets.

Base Code gives your team a shared cloud environment for an existing codebase without setting up a local development environment. Use the AI chat to make changes on branches, preview your work, and open pull requests for review. GitHub stays the source of truth.

Using Base Code

Before you begin: Your project must be a web or full-stack project in a GitHub repository.

Setting up Base Code

Connect a GitHub repository to make changes with the AI chat in Base Code. If your GitHub account is already connected, continue to choosing a repository.

Connecting your GitHub account

Connect your GitHub account and give Base44 access to the repositories you want to work on.

To connect your account:

1. Go to Base Code.
2. Click Connect GitHub.
3. Sign in to GitHub if prompted, then authorize Base44 Builder.
4. Select the GitHub account or organization, then follow the prompts to install or configure Base44 Builder and give it repository access.

Choosing a repository

Choose a repository and branch to open in Base Code.

To choose a repository from your account:

1. In Base Code, click View more.
2. Select a repository.
3. Under Branch, keep the selected branch or select another.
4. Click Connect.

Tip:

• To open a listed repository on its default branch, select it on the Base Code page, then click Open in Base.
• To connect another repository, select Add repository from the repository drop-down.

Working on your project

Use the AI chat to make changes to your connected repository and test them in a development preview.

If setup changes are required and you connected the default branch, Base Code creates a setup branch and commits them there. If you connected another branch, Base Code commits any setup changes directly to that branch. To include unmerged setup changes in a new branch, start from the branch containing those changes.

Note: Base Code provides a development preview, not production hosting. To release your changes, use your project’s existing deployment process.

Making your first change

Describe the change you want to make. Base Code creates a new branch and names it based on your request. To work on an existing GitHub branch instead, import the branch to Base Code.

To make your first change:

1. Go to Base Code.

2. (Optional) If a drop-down appears next to Create new branch, select the branch to start from.

3. In the prompt box, describe the change you want to make. For example:

   Add a dark mode toggle to the settings page, and remember the choice between visits.

4. Click Create branch to open the new branch and start making changes.

5. Review the change in Preview, then ask the AI chat for any adjustments.

Saving your work

Base Code saves your work as you go. As you chat, it commits and pushes to your working branch on GitHub.

To review what’s on your branch, ask the AI chat. To bring those changes into your default branch, open a pull request, review the changes, then merge.

Opening a pull request

After testing your changes, open a pull request for review. When your workspace uses each person’s GitHub connection, your account needs write access to the repository. Opening a pull request doesn’t automatically merge your changes.

To open a pull request:

1. Click Create PR at the top of the editor.
2. Enter a Title and a Description (optional).
3. Click Create PR.
4. In Your PR is ready, open the link under Link to PR to review your changes in GitHub.

Tip: You can also ask the AI chat to create a pull request. It writes the title and description for you.

Resolving branch conflicts

If your pull request has conflicts, the AI chat can resolve them for you. Resolving conflicts merges the pull request’s base branch into your working branch.

To resolve conflicts:

1. Click Resolve conflicts above the prompt box.
2. Review and test the changes the AI makes, especially where both branches changed the same feature.

Answering review comments

Use the AI chat to address feedback on your pull request.

To address review comments:

1. Ask the AI chat to list unresolved comments on your pull request. It includes the file and line for each thread.
2. Tell it which comments to address and what to change.
3. Review the proposed changes and replies before asking it to post.
4. Ask the AI chat separately to resolve a thread when you’re ready.

Managing branches

Create a new branch or import an existing one to work on separate changes. Each branch has its own development environment in Base Code. To switch branches, click the branch drop-down above the AI chat and select a branch.

Creating branches

Create a branch from your repository’s default branch or another active branch.

To create a branch:

1. Click the branch drop-down above the AI chat.
2. Click Create new branch.
3. Select the starting branch from the drop-down next to Start from.
4. Describe your change in the AI chat and send the message.

Importing a branch from GitHub

Import an existing GitHub branch to continue working on it in Base Code. AI chat changes are committed and pushed to that branch.

To import a branch:

1. Click the branch drop-down above the AI chat.
2. Click Import from GitHub.
3. Select the branch.
4. Click Import.

Deleting a branch

Deleting a branch removes it and its chat from Base Code. The branch remains on GitHub.

To delete a branch:

1. Click the branch drop-down above the AI chat.
2. Click More actions next to the branch, then click Delete.
3. Click Delete branch to confirm.

Managing your project

Use your app’s dashboard to manage project files, secrets, and development services.

Adding secrets

Add API keys and other secrets your project needs. The AI chat prompts you when a secret is required. Secrets are encrypted, kept out of your repository, and shared across branches, including after a rebuild.

Changes and removals apply automatically to running branches. Inactive branches pick them up when you next open them.

To add a secret:

1. Click Dashboard at the top of the editor.
2. Click Secrets.
3. Click Add Secret.
4. Enter the Secret Name and Secret Value, then click Add Secret.

Tip: To add secrets in bulk, click Import .env, then upload or paste your file. Each KEY=VALUE line becomes a secret. An existing secret with the same name is overwritten.

Collaborating with teammates

Your team can use the AI chat to contribute to the same project and review changes through pull requests.

Workspace owners, admins, and editors can access the Base Code project without a separate app invitation. To invite someone outside your workspace, add them as a collaborator from the app editor.

FAQs

(FAQ content not included in this extraction.)

Original source

Base44 backs up your app data automatically as it changes. Review what your tables held earlier, download a copy as CSV, or restore your data to that point.

Base44 automatically backs up your app’s data as it changes. If records are edited, imported, or deleted by mistake, you can look back at what your tables held earlier, download a copy, or restore your data to that point in time.

Warning

Backups are available on the Elite and Enterprise plans. Elite workspaces keep 7 days of backups, and Enterprise workspaces keep 30 days.

How backups work

Backups run automatically on eligible plans, so there is nothing to switch on. As your data changes, Base44 saves the earlier state of your tables so you can review it, download it, or put it back. Backups cover the table data Base44 manages for your app.

Tip

Good to know:

• Backups apply to your whole workspace, and they start from the moment the feature becomes active on your plan.
• How far back you can go depends on your plan: 7 days on Elite, and 30 days on Enterprise.
• Only people with editor access to an app, such as its owner or an invited editor, can view, download, and restore backups.
• Backups cover your data only. Your app’s code and design have their own history, which you reach from Version History in your app editor.

Viewing your backups

The Backup & Restore tab lists every backup for your app, newest first, with your current data at the top. Each entry shows when it was taken and how many tables changed at that moment, and you can expand it to see the tables themselves.

To view your backups:

1. Click Dashboard in your app editor.
2. Click Data, then click the Backup & Restore tab.
3. Click the date filter, which reads Last 30 days to begin with, to narrow the list to a period or a custom range.
4. Click All tables to limit the list to the tables you care about.
5. Click an entry to see which tables changed.

Tip

To go straight to one table’s backups, click the More actions icon on that table’s card in Tables, then select Backup & Restore. The tab opens with the table already selected in the filter.

Restoring your data

Restoring rewrites your records so they match a point in time you choose. You can put back a single table or every table in your app at once, and you can undo a restore afterwards.

Warning

Editing pauses while a restore runs. Nobody can edit the tables being restored until it finishes, and apps with more records take longer.

Restoring one table

Restore a single table when only that table’s data went wrong. Every other table keeps its current data.

To restore one table:

1. Click Dashboard in your app editor.
2. Click Data, then click the Backup & Restore tab.
3. Find the point in time you want, using the date filter if you need it, then click the entry to expand it.
4. Next to the table you want, click the Restore this table icon.
5. Review the confirmation, then click Restore table.

Restoring every table

Restore everything when a change affected your app as a whole, such as a bad import or a bulk delete that touched several tables.

To restore every table:

1. Click Dashboard in your app editor.
2. Click Data, then click the Backup & Restore tab.
3. Find the point in time you want, using the date filter if you need it.
4. Click Restore to here on that entry.
5. Review the confirmation, then click Restore all data.

Note

If your app has a large number of tables, Base44 asks you to restore them one at a time instead. Use the Restore this table icon on each table you need.

Undoing a restore

Base44 saves your current data before a restore starts, so a restore is reversible. The confirmation tells you how long you have to change your mind.

To undo a restore:

1. Click Undo in the message that appears in your app editor when the restore finishes.
2. Review the confirmation, then click Undo restore.

Note

If you have closed that message, open the Backup & Restore tab and restore to the point in time just before the restore ran. Records added since the restore are removed when you undo it.

What a restore changes

A restore rewrites the records in the tables you chose so they match the point in time you picked. Nothing else in your app changes.

• Record IDs stay the same. Records that were changed or deleted keep the ID they had before, so links from other tables still point to the right record.
• Field values come back exactly as they were at that point, including fields that link to records in other tables.
• Records added after that point go to trash rather than being deleted for good, so you can bring them back from there within 30 days.
• Restoring one table leaves the others alone. If related tables need to match, restore all of them to the same point in time, otherwise a link can end up pointing at a record that no longer exists.
• Restores run on production data only. If you are viewing test data, switch to production first.

Note

If a table’s structure changed after the point you picked, Base44 warns you in the confirmation window. Fields that no longer exist in your table are not restored.

Downloading a backup

Download a table as it was at an earlier point to keep a copy outside Base44, or to check what changed before you decide whether to restore.

To download a backup:

1. Click Dashboard in your app editor.
2. Click Data, then click the Backup & Restore tab.
3. Find the point in time you want, using the date filter if you need it, then click the entry to expand it.
4. Next to the table you want, click the Download CSV icon.

FAQs

A few things people ask about how backups behave.

Original source

Launch and manage Google Ads campaigns from your Base44 app dashboard

Base44 uses your app’s own content to generate the ad copy, images, and logo for you.

Go from building your app to getting it in front of the right people with Google Ads. Create campaigns using your app’s existing content, manage your budget, and track results directly from your app dashboard. Google Ads Performance Max campaigns will help you reach and convert your next best customer across Google Search, YouTube, Gmail and more.

One campaign, running across Google

Tip

Before you begin:

• Your app must be published, and its visibility set to Public (login required) or Public (no login). A private or workspace-only app cannot be advertised.
• Google Ads campaigns are billed separately from your Base44 subscription.
• Google does not allow ads for some content and products, and restricts others. Review the Google Ads policies before creating a campaign.
• You need an active payment method to complete setup.

Creating and launching a campaign

Create and launch a campaign from your app dashboard. Google Ads sits under Marketing, alongside SEO & GEO and Social content. Base44 uses your app’s content to generate your campaign assets, including headlines, descriptions, images, and your logo.

Base44 detects your app’s language automatically and generates your ad copy in that language, including for non-English apps. The preview beside your assets shows how your ad looks on Search, Gmail, YouTube, and Display.

Note

Limits and requirements:

• You can have 2 active campaigns at a time. To start a third, pause one of the campaigns you are already running.
• Images you upload must include a landscape image at 1.91:1 and a square one at 1:1, and portrait sizes are optional. A logo must be square and at least 128 by 128 px. Files can be JPG, PNG, or GIF, up to 5 MB each.
• If your campaign targets locations in the European Union, Google asks you to declare whether it runs political ads before you launch. Google no longer allows political ads in EU countries, so declaring that your campaign has them stops your ads showing to people there.

To create a campaign from your app dashboard:

1. Go to your app’s dashboard.
2. Click Marketing.
3. Click Google Ads.
4. Click Get started for your first campaign, or + New Campaign to add another.
5. In Review assets, review your campaign details and assets:
   • Under Campaign details, check your campaign name, business name, and phone number. Only you see the campaign name, in your Google Ads account, while your business name and phone number can appear in your ads.
   • Next to Site page that your ad will lead to, choose the page people land on after clicking your ad. Leave the page empty to use your main page.
   • Under Site links, click Add site link to point people at specific pages as well. You cannot change the domain after the campaign is created.
   • To edit a headline or description, click the pencil icon next to it.
   • To regenerate headlines or descriptions in a section, click Regenerate.
   • For images, click Generate more to add more options, or click Add, then click Regenerate all to replace all images.
   • To upload your own image or logo, click Add, then select Upload image or Upload logo.
6. Click Continue.
7. In Set daily budget, choose a preset amount or set your own daily budget within the range shown on screen.
8. Click Continue, or Validate payment and continue if you do not have a payment method on file yet.
9. In Targeting & tracking, choose where your ad runs and what people search for:
   • Under Where your ad runs, add or remove locations to match where you sell. With none selected, Google shows your ad worldwide.
   • Under What people search for (keywords), edit the search themes suggested from your app.
   • Under Track your success, click Set up tracking with AI, send the prepared message in the chat, then publish your app so the tracking goes live. This card does not appear if your app already tracks conversions.
10. Click Approve and Launch. If you do not have a payment method on file, click Verify payment method first and add one.

The three steps of the campaign wizard

Budget, billing, and credits

Your daily budget sets the pace of your spend, Base44 charges you for the clicks your campaign gets, and any ad credits you have come off those charges automatically.

Understanding your daily budget

The amount you set is a daily average budget, not a hard daily limit. Google spends more on days when it sees a good opportunity for your app and less on quieter days, so your spend moves up and down from one day to the next.

On a busy day, Google can spend up to twice your daily average budget. It balances that out with lower spend on other days, and your account also has an overall monthly ceiling that your total spend stays within.

Getting charged for your campaign

You are charged for estimated ad clicks from your current billing cycle, plus a 15% Base44 service fee.

• How often: New ad accounts are charged every 3 days, and accounts created earlier are charged once a week. Your budget screen shows how often your own account is charged.
• Adjustments: Each month, Google’s final costs may adjust your next payment. VAT may apply based on your billing country.
• Failed payments: These can pause or block your campaign. If your 14-day grace period ends without a successful payment, update your payment method to reactivate Google Ads.

Keeping access while a payment is overdue

When a payment is overdue, a notice appears on your Google Ads dashboard with a Fix payment link that takes you straight to settling the balance.

You do not lose sight of your account while that notice is up:

• What you can still see: Your dashboard, your campaign list, and each campaign’s detail and editor all stay open, so you can keep reading performance while you sort the payment out.
• What you cannot do: Everything is read-only until the balance is paid. Changes are refused even if you reach an edit screen another way.
• How far it reaches: The hold applies to the whole workspace. If any Google account in your workspace has an unpaid balance, Google Ads pauses for everyone until each past-due balance is paid.

Tracking your ad credits

When you have ad credits available to spend, your Google Ads dashboard shows your Ad credit balance.

Ad credits apply to your Google Ads charges automatically. You do not need to redeem or activate them.

Some campaigns qualify for an offer from Google that adds ad credit once your campaign spends a set amount in its first 60 days. The offer is for new advertisers only, and the reward and the spend it requires are both shown on screen before you launch. Google’s terms apply.

The Google Ads dashboard also shows a notice when:

• Ad credits are added to your account.
• Ad credits are nearing expiration.
• Ad credits expire before you spend them.
• Ad credits are fully spent, so your next charge is billed in full.

Monitoring campaign performance

Monitor your Google Ads campaign from the Google Ads dashboard. Review your campaign status, budget, spend, clicks, conversions, impressions, and results over time. Select a preset date range, or choose Custom to review performance for a specific period.

Warning

A new campaign starts in a learning period, where Google’s AI works out the best way to put your app in front of the right people and spend your budget efficiently. Most campaigns settle within 14 to 21 days, and learning runs for up to 4 weeks of active serving time.

Pausing your campaign or making major changes during this time, and especially in the first 3 days, delays your results. Pausing does not restart learning, so Google picks up where it left off when you resume, but it takes time to get back up to speed.

After launch, your campaign moves through two phases:

• Campaign review: Google checks your ad against its advertising policies. This usually takes 1 to 2 days.
• Campaign optimization: Google learns from your early traffic and tunes delivery. This is the learning period, and it runs for up to 4 weeks of active serving time.

Note

When a campaign needs action, its status changes to Needs attention. Open the campaign to review the issue and follow the steps shown.

To monitor your campaign:

1. Go to your app’s dashboard.
2. Click Marketing.
3. Click Google Ads.
4. Click the campaign you want to review.
5. Review your campaign performance.

Setting up conversion events

Conversion events tell Google Ads which actions count as a win, such as a sign-up, a form submission, or a purchase, so it can spend your budget on the people most likely to take them.

You normally set these up while creating a campaign. Use the steps below if your campaign is already running and its setup card asks you to add events, or if the card reports that the tag it found in your app does not match this campaign.

To set up conversion events on a running campaign:

1. Open the relevant campaign from your Google Ads dashboard.
2. In the conversion events setup card, click Add to chat.
3. Send the prepared message in the AI chat to add the required events to your app.
4. Publish your app so the events take effect.

Managing your campaign

Open a campaign from the Google Ads dashboard to edit its details, change its daily budget, pause it, resume it, or archive it.

To manage your campaign:

1. Go to your app’s dashboard.
2. Click Marketing.
3. Click Google Ads.
4. Select the campaign you want to manage.
5. Choose what you want to do:
   • Click Edit campaign to update your campaign details.
   • Click Manage budget to change your daily budget.
   • Click Manage conversion goals to choose which of your events this campaign focuses on. By default it optimizes for all of them, and changing this restarts the learning period.
   • Click Pause temporarily to pause an active campaign.
   • Click Resume campaign to restart a paused campaign.
   • In the campaign details, click Edit keyword themes to adjust the searches your ads target, and to add excluded terms that stop your ads showing on searches you do not want.
   • Open a text asset to edit it, or open an image or logo asset to upload a replacement.
   • Open the Manage menu, then click Archive campaign to archive a campaign you no longer need.

Note

If you pause a campaign during a billing cycle, you are still charged for any campaign activity before the pause.

FAQs

Click a question below to learn more.

• Do I need a Google Ads account?
• Does generating campaign assets use credits?
• Are ad credits the same as Base44 credits?
• Can I import a campaign from another app?
• Can I change my budget after launching?
• Why is my campaign getting less traffic than expected?
• Why was I charged a different amount than my daily budget?
• Why was my campaign paused?

Original source

Connect a GitHub repository to Base44 so your whole team can make changes in plain language, while your own repository stays the source of truth for the code.

Connect your GitHub repository to Base44 and keep building it. Everyone on your team can ship real changes, and your repository stays the source of truth.

Build from anywhere

Work on your project from desktop or mobile. Base44 runs it in the cloud, so there is nothing to install.

Bring your team

Teammates can make changes to the codebase with the AI chat, even if they do not run code locally.

Keep your GitHub workflow

Each change saves to a branch in your repository, and you open a pull request when the work is ready.

Multiple AI models

Use any AI model available in Base44, without managing separate subscriptions.

Connecting your repository

Connect a repository from your GitHub account or paste a repository URL. Base44 checks it, creates the project, clones the code, configures it, and starts the preview. Connect your GitHub account to save your work.

Before you begin:

• You need to be an owner, admin, or editor in the Base44 workspace where you want to import the project to.
• Your project runs as a web service on Base44, so your repository must be a web or full-stack app that can be built and run from source in Docker, such as a frontend with an API or a server-rendered site.
• For private repositories, install the Base44 GitHub App so it can access the repository.
• Your workspace can limit Editors to importing repositories from approved GitHub organizations. If a repository is not in an approved organization, ask a workspace owner or admin to add it under Settings > Governance > GitHub organizations. Workspace owners and admins can import from any GitHub organization.

From your GitHub account

Connect a repository directly from your GitHub account. If you don’t own the project, paste a link instead and Base44 creates a copy you own.

To connect from your GitHub account:

1. From the Base44 home page, click the + icon in the prompt box.
2. Click Connect your repo.
3. Connect your GitHub account if it is not connected yet.
4. Choose the repository to connect.
5. Click the Branch drop-down to select a starting branch. Base44 uses your default branch if you don’t choose one.
6. Click Connect.

From a repository URL

Paste a GitHub repository URL to connect a repository, public or private. Base44 checks your access to it, then either connects it directly or creates a copy in your GitHub account first. When the original is private, your copy is private too.

To connect using a repository URL:

1. From the Base44 home page, click the + icon in the prompt box.
2. Click Connect your repo.
3. Click Paste a link.
4. Paste the link to the GitHub repository.
5. Choose based on your access:
   • Branch: Select a starting branch if you can push to the repository.
   • Your copy on GitHub: Enter a name for the copy Base44 creates if you can’t push to the repository, then choose its visibility:
     • Fork (public): Linked to the original, so you can send your changes back to it.
     • Private copy: Only you can see and edit it, and it is not linked to the original.
6. Click Connect. If you are creating a copy, click Fork and connect or Copy and connect.

Limiting repositories to approved GitHub organizations

Your workspace can restrict which GitHub organizations its repositories come from. When GitHub organizations is on, apps in the workspace can only create or import repositories in the organizations you approve. Apps that are already connected to GitHub aren’t affected.

Before you begin:

Only workspace owners and admins can approve organizations, and the policy does not restrict them.

To limit repositories to approved organizations:

1. Click your workspace name at the bottom left of your account.
2. Click Settings.
3. Click Governance.
4. Turn on the toggle next to GitHub organizations.
5. Under Allowed organizations, select each organization you want to approve.

For everyone else in the workspace, the organization pickers show only the approved organizations. If you try to use a repository from an organization that is not on the list, Base44 tells you your workspace limits repositories to approved organizations. Ask an owner or admin to add the organization, then try again.

Working on your project

When your project import is complete, continue building with the AI chat and see your changes in Preview. Switch to Dashboard to browse your files in Code and manage the values your project needs to run in Secrets.

Saving your work

Base44 saves your work as you go. When you import, it creates its own setup branch named base44/setup- followed by a short ID, and runs setup there. From then on, it commits and pushes to the branch you’re working on each time the AI chat finishes a change. Branches you create later get short descriptive names, like dark-mode-toggle. Your default branch is never touched.

If you imported a public repository without connecting GitHub, your app runs in local mode. Nothing is committed or pushed, and Create PR is disabled. Edits you make yourself in Code are committed the next time the AI chat finishes a change.

An imported project uses the git branches in your repository directly, so git stays the source of truth. Branches work the same as they do in any Base44 app, with a few differences. There is no merge or update from your default branch inside Base44, all branches share one sandbox, and deleting a branch in Base44 leaves the branch on GitHub. See working with branches.

Resolving sync conflicts

If your repository and your Base44 app both change the same file, the sync leaves a conflict. The AI chat raises a card for it, reads every conflicted file, and rewrites each one so both sides’ changes survive, then pushes the result back to your repository as a merge commit.

Where the two versions genuinely disagree, such as when each side implemented the same feature differently, the AI asks you which behavior you want before it writes anything.

Approving writes to your repository

When the AI needs to write files straight to your connected repository, it asks you to approve first rather than pushing on its own. Review what it plans to do, then approve or reject it in the chat.

Adding secrets

When your project needs an API key or other secret to run, the AI chat asks you for it. Give it the value, and Base44 stores it encrypted and applies it to your project, including after a rebuild. Changing or removing a secret takes effect without republishing, and reaches your live app and every branch you have open. A secret is never committed to your repository, and it is shared across all branches, so you enter each one only once.

You can also add and manage secrets in your app’s dashboard.

To add a secret:

1. Go to your app’s dashboard.
2. Click Secrets.
3. Click Add Secret.
4. Enter the Secret Name and Secret Value, then click Add Secret.

Tip: To add secrets in bulk, click Import .env, then upload or paste your file. Each KEY=VALUE line becomes a secret, and any existing secret with the same name is overwritten.

Shipping your work

Every change is committed by base44-builder[bot]. A shared branch produces one pull request for the whole team, and separate branches each get their own. Teammates with editor access share the project and its secrets.

Opening a pull request

The pull request goes from your working branch into the branch it was created from, with a note crediting Base44 and a link back to your project. The setup pull request always goes into the branch you imported.

Once the pull request is open, your changes keep saving to the same branch so reviewers always see your latest work and any checks run again on each push.

To open a pull request:

1. Click Create PR at the top of the editor.
2. Enter a Title and a Description (optional).
3. Click Create PR.

Tip: You can also ask the AI chat for a pull request, and it drafts the title and description for you.

Note: If you haven’t granted permissions yet, click Review permissions on GitHub and have an account owner approve it.

Answering review comments

Handle your reviewers’ feedback from the AI chat, without leaving Base44.

Ask the AI chat for the review comments on your pull request, and it lists each unresolved thread with the file and line it points at. Tell it what to change, and it drafts a change and a reply for each one. Nothing is posted to GitHub until you approve that specific draft. Resolving the thread is a separate step you ask for. You can also ask it to comment on the pull request itself.

Everything it posts appears as base44-builder[bot]. Merging happens on GitHub, exactly as it does today.

FAQs

Click a question below to learn more about importing and working on a GitHub project.

Original source

Learn how you and your Superagent share notes

Create and edit notes, keep them updated from your email, calendar, and chats, and share them with a public link.

Notes is a shared space where you and your Superagent keep the information you both work from. Your Superagent creates and updates notes as it learns about your work, and you can read them, edit them, and add notes of your own. Open Notes in the sidebar to see them.

Tip: To jump straight to this page, add /notes to the end of your Superagent’s web address, or bookmark the page.

How notes work

Your Superagent organizes what it knows into notes by topic, such as your projects, the people you work with, or your travel plans. Notes link to each other, and each note shows the notes it connects to, so related information stays together. At the top of the list, the pinned For you note tracks your current priorities, anything that needs your attention, and your upcoming calendar items.

The Notes list, with the pinned For you note at the top

When your Superagent references a note in chat, the note opens in a side panel beside the conversation, so you can read it without leaving the chat. You can also attach notes to a message so your Superagent uses them as context.

Reviewing your notes

Read through what your Superagent knows, starting from the For you note.

To review your notes:

1. Open your Superagent.
2. Click Notes in the sidebar.
3. Click a note to open it, or click the search icon to find one by name.

Opening a note from the Notes list

Creating a note

Add your own notes alongside the ones your Superagent creates. Write one from scratch, or keep something your Superagent has already told you.

Writing a note yourself

Start a blank note and build it out with the elements you need.

To create a note:

1. Open your Superagent.
2. Click Notes in the sidebar.
3. Click Add new note.
4. Give the note a title, then type its content. Notes save automatically as you write.
5. Press / or click the Add block button to add elements such as headings, lists, images, and tables.

Adding an element to a note from the add block menu

Saving part of a conversation

Keep something your Superagent said without retyping it.

To save a selection as a note:

1. In your Superagent conversation, highlight the text you want to keep.
2. Click Add note.
3. Click View note in the confirmation to open it.

Saving a highlighted passage from a conversation as a note

Everything you save from the same conversation goes into one note, so highlighting another passage later adds to that note instead of starting a new one.

Adding a kanban board to a note

A note can hold a live kanban board, so you can track work in the same place you and your Superagent keep everything else. A board is text underneath, where each column is a heading and each card is a list item, so you can build it visually or write it out.

A kanban board inside a note, with Todo and Done columns

To add a board:

1. Open the note, then click in its body where you want the board.
2. Press / or click the Add block button, then select Kanban board. The board starts with a Todo and a Done column.
3. Build it out:
   • Add a card: Click Add card in a column, then type the card text.
   • Add a column: Click Add column to the right of the board, or select Add column after from a column’s menu. A new column arrives titled New column with your cursor at the end of it, so clear that text before typing your own title.
   • Move a card: Drag it to another column, or select Move to from the card’s menu.
   • Rename or reorder a column: Select Rename column, Move left, or Move right from the column’s menu.
   • Remove something: Select Delete card or Delete column.
   • Edit it as text: Click Show raw text on the board, then Hide raw text to go back to the board.

A board also appears in a note you share to the web, laid out and ready to read.

Keeping your notes up to date

Your Superagent keeps notes current as you chat with it. You can also refresh them from your connected data at any time.

To refresh your notes:

1. Open your Superagent.
2. Click Notes in the sidebar.
3. Click Update notes.
4. Click Refresh data. Your Superagent reviews your available email, calendar, and conversation data and updates your notes.

Confirming a refresh of your notes from your connected data

Managing a note

Duplicate, share, or delete a note from its More actions menu. The note’s row in the list has a quick menu for duplicating and deleting, and the open note has the full menu, including sharing.

To manage a note:

1. Open your Superagent.
2. Click Notes in the sidebar.
3. Open the note, then click the More actions icon at the top right.
4. Do one of the following:

Managing a note from its More Actions menu

• Duplicate a note
• Share a note to the web
• Delete a note

Opening notes beside your chat

Open the notes panel yourself at any time, without waiting for your Superagent to reference a note. The panel docks beside your conversation, so you can read a note and keep chatting.

Notes docked beside your conversation

To open notes beside your chat:

1. Open your Superagent.
2. Open a conversation, or click New conversation.
3. Click the Open notes icon at the top right.

Note: From the docked panel, you can:

• Open a note: Click it in the panel’s list.
• Switch notes: Click the note title at the top of the panel, then select another note, or select All notes to go back to the list.
• Read a note in full: Click the More actions icon, then select Open full page.
• Close the panel: Click the Close note icon, or click the Open notes icon again.

FAQs

Click a question below to learn more about notes.

• What is the difference between notes and memory?
• What is the difference between notes, files, and data?
• Who can see my notes?
• Where do meeting notes go?

Original source

Connect your app to popular tools like Google Workspace, Slack, Salesforce, GitHub, Snowflake, and Databricks using managed integrations.

Connectors let your Base44 app work with the tools and data your business already uses. Connect services like Gmail, Slack, Google Workspace, Snowflake, Databricks, and more, then ask the AI chat to help you build app flows that use them.

About connectors

Connectors link your app to the tools you already use. Pick a tool, authorize it, and let Base44 handle the setup behind the scenes, no API keys, no manual config.

Tip

Need more control over a specific API? Use a custom integration.

Connector types

There are two types of connector, based on whose account the connection uses.

Connectors for app users

Each person using your app connects their own account. The app acts on their behalf, and their data stays private to them.

Best for per-user actions, like a CRM where each sales rep sends email from their own Gmail.

Connectors for app builders

You connect a tool once at the workspace level, and the app uses that one connection for everyone.

Best for a shared account or a data platform, like Slack alerts to your team’s channel, or a dashboard that queries Snowflake.

Browsing available connectors

Find connectors in the Integrations tab of your app’s dashboard. Search for a specific connector or use the filter to sort the list.

You can also tell the AI chat what you want to connect and how you want to use it, and get relevant suggestions based on your app’s structure, pages, and data.

To browse the full list with categories and example prompts, see the connectors catalog.

Send reports and alerts

Email reports, alerts, or summaries through Gmail or Outlook.

Generate documents and files

Create documents, spreadsheets, presentations, or files using Google Workspace tools.

Manage events and availability

Create and manage events or availability using Google Calendar or Outlook.

Notify your team

Send notifications or updates to teams through Slack.

Track code and issues

Track code activity, issues, and pull requests with GitHub.

Query data and build dashboards

Query external data and build dashboards with Snowflake or Databricks.

Request a connector

You can also request a connector to add to Base44. Go to Integrations in your app’s dashboard and click Request a connector at the bottom.

How connectors work in your app

Once you connect a tool, you can reuse it across pages, flows, and backend functions. In the AI chat, ask Base44 to build pages, tables, dashboards, or automations that read from or write to the connector.

When you include a connector in a flow, Base44 creates a backend function in Dashboard → Code → Functions. Open that function to review the generated code. You can edit it yourself or prompt the AI chat to update it. For example:

Send a Slack message to #product-updates when this function runs.

If you later add a flow that needs extra permissions, you may be asked to review and approve the new actions and permissions for that tool.

Registering callback URLs

When you set up a connector with your own OAuth credentials, you register a callback URL with your OAuth provider so it knows where to send people back after they authorize. Base44 uses one callback URL for every app in your workspace.

Using the single callback URL

Every connector you add uses one callback URL for all of your apps, so you register it with your OAuth provider once and it keeps working as you build more apps and connect custom domains.

Add this URL to your OAuth provider’s allowed redirect URIs:
https://connectors.base44.com/api/oauth/callback

Viewing your callback URLs

You can check the single callback URL at any time, and look up the per-app URLs for a specific app.

To view your callback URLs:

1. Click your workspace name at the bottom left.
2. Click Settings.
3. Click Connectors under Plugins.
4. Under Connectors For App Users, click View redirect URIs for your apps.
5. Find the single callback URL under Callback URL.
6. (Optional) Expand Per-app URLs (for legacy connectors), then select an app to see its per-app URLs.

Switching an older connection

Connections you added before August 17, 2026 register a separate URL for each app host, and they show a Per-app URLs badge next to their name. Each connection is switched over on its own, so one connector can have some connections on the single callback URL and others still on per-app URLs.

Switching is worth doing if you are adding apps or custom domains and are tired of registering a new URL each time. If your setup is stable and working, there is no need to switch. Existing connections keep working on their per-app URLs for as long as you leave them there.

Warning

Keep your existing per-app callback URLs registered with your provider when you switch. App users who connected before the switch still need them, and changes in your provider can take a few minutes to take effect.

To switch a connection to the single callback URL:

1. Click your workspace name at the bottom left.
2. Click Settings.
3. Click Connectors under Plugins.
4. Under Connectors For App Users, next to the connector, click View.
5. Under Connections, next to the connection you want to switch, click Edit.
6. Under Callback URLs, click Switch to a single URL.
7. Add the URL shown to your OAuth provider’s allowed redirect URIs.
8. Select I’ve added the URL to my OAuth provider, then click Switch.

Note

To move a connection back later, open it again and click Switch back to per-app URLs. Check that your provider still has the per-app URLs registered first, because a connection created on the single callback URL may never have had them.

Managing your connectors

From Integrations in your app’s dashboard, you can view and manage your app’s connectors, review what each can access, and switch, disconnect, or reconnect the connected account per tool as needed.

For connectors for app builders, reconnect from Integrations → My integrations. For connectors for app users, each person reconnects their own account from inside your app.

To manage a connector:

1. Go to your app’s dashboard.
2. Click Integrations.
3. Click the My integrations tab.
4. Find the connector.
5. Click the More actions icon (···) and choose an option:
   • View access to see the connector’s current permissions.
   • Switch account to connect a different account.
   • Reconnect to restore an expired connection.
   • Disconnect to remove the connection from this app.
   • Remove to delete the connector.

Controlling workspace availability

The steps above manage the connectors in one app. On the Enterprise plan, workspace owners and admins can also decide which external services are available across the whole workspace, so a connector you disable is blocked everywhere it is used, including in apps, Superagents, and in-app agents.

You can review which apps rely on a connector before you disable it, and you can allow or block several connectors at once. The two credential types are managed separately, so a service can stay enabled as a Shared Credential while being disabled as an App User Credential.

For the steps, see Managing connector availability for your workspace.

FAQs

Common questions about connecting tools to your app.

Can I connect multiple tools to my app?

Why do I need to reconnect a connector?

Original source

About the template marketplace

Explore ready-to-use app templates from the Base44 community and your workspace. Find inspiration, launch your next project in minutes, or publish your own.

The template marketplace is your shortcut to building great apps on Base44. Browse a wide range of ready-made templates created by talented creators in the community. If you are unsure where to start or want to skip hiring a partner, templates make it easy to get going right away. Just choose a template and customize it to fit your needs.

If you prefer to keep templates private to your team, you can create workspace templates instead of listing them publicly. Workspace templates reuse your app across a single workspace without appearing in the public marketplace. Learn how to create and manage workspace templates.

You can also publish your own public templates for others to use, reaching a wider audience while showcasing your skills. For internal-only use, keep templates as workspace templates so they are available only to your team.

Accessing templates

Go to App Templates in the Community tab in your workspace to browse all available templates. Templates with reviews display an average rating to help you evaluate them before choosing one.

App Templates include:

• Community: Templates shared by the community and available to all Base44 users.
• Workspace: Templates created and saved by your team. Workspace templates are private to your workspace, and only members of your workspace can see them.

When you use a template, it is copied into your own workspace where you can rename it, change the content, update the design, and modify how it works.

Notes:

• You need to be logged in to your Base44 account to view and use app templates.
• If you want to use a template that uses backend functions, you need to have a Builder plan or higher.

To access app templates:

1. In your Base44 workspace, go to App Templates.
2. Hover over a template and click View details to see more information, images, usage stats, ratings, and reviews.
3. (Optional) Use the Workspace tab to view templates created and saved in your workspace. These templates are only visible to members of your workspace.
4. Click Use Template.

Creating public templates

You don’t need to create something complex to share as a public template. Simple apps, reusable layouts, or creative tools can all be helpful to others. If you have made something useful or fun, you can add it to the community app templates library. You can share your template with the whole Base44 community for free.

Before you start, check that your app qualifies. You need to own the app and have published it at least once, and you need to be an admin of the workspace that owns it. An app you started from someone else’s template cannot be listed again. When someone uses your template, it is copied into their workspace and your original app stays the same.

Before submitting your app, make sure:

• You test it to ensure it works and includes full functionality.
• You add real-looking sample content.
• Your app is secure. Learn more about security and using the security check.

You start a template from your app’s dashboard settings.

To create a public template:

1. Click Dashboard in your app editor.
2. Click Settings.
3. Next to Create App Template, click Create template.
4. Select Public template, then click Continue.
5. Under Basic info, enter a Template name and a Description of what makes your app worth trying.
6. Under Categories, select at least one category that describes your app.
7. Under Template screenshots, click Add screenshot and upload at least 3 screenshots, up to 7.
8. Select the I agree to the Base44 Terms and Marketplace Terms checkbox.
9. Click Create template at the top right.

Screenshot guidelines

• Your first screenshot is the template’s cover and must be 16:9, such as 1920x1080. Use the crop icon if it is not.
• To take fresh captures, click Preview app to open your published app.
• Show your app in action with real-looking data, and use clean, full-screen views.
• Avoid blurry or empty screens.

Improving your listing

If you want your template to stand out, start by focusing on solving a clear problem for others and choosing a catchy title. Add a helpful image and description that show your app in action and make its purpose easy to understand.

The most successful templates have clear and friendly language, and include strong visuals that highlight your app’s value.

Tips for improving your listing

Description:

• Say clearly what your app is for and who it helps
• Use short, friendly sentences
• Avoid overly technical or complex language

Tags and categories:

• Pick tags that describe what your app does (like “productivity” or “social”)
• Avoid adding too many tags

The approval process

After you submit your listing, the Base44 team reviews it to make sure it meets community guidelines. Listings that don’t follow these guidelines may be rejected. If your app is approved, it appears in App Templates for others to discover and use.

Base44 may decline or remove a listing if:

• Spam or broken: The app listing is spam or is not functioning.
• Private setting: The app is set to private, which prevents others from viewing it.
• Community rules violation: The app includes content that breaks community rules.
• Screenshots do not match: The submitted screenshots do not reflect the actual appearance or features of the app.
• Missing security settings: Apps must complete a security check to be eligible for publishing.
• Broken functionality: Some features in the app are not working as intended.
• Invalid or non-compliant app name: The app name uses terms like “template,” version numbers, or other values not allowed by store policy.
• Duplicated app without chat: If your app is a duplicate and does not include chat functionality, please send the original app with chat history.
• Mismatched categories: The categories selected do not match the app’s purpose or functionality.
• App has never been published: Apps must be published at least once before being submitted for review.

Important:

• Final approval depends on Base44’s internal guidelines. The team may remove listings that do not meet broader community quality standards, even if a specific reason is not listed above.
• The approval process may take some time. We appreciate your patience.

Updating your template

Your template stays linked to the app you created it from, so what you need to do depends on what changed.

• App functionality or design: Publish your app as usual. Anyone who uses your template from then on gets the latest version, and you do not need to resubmit it.
• Listing details: Changes to the name, description, categories, or screenshots go back through review before they appear in the catalog.

Either way, people who already added your template keep their own copy, and your changes do not reach it.

To update your listing:

1. Click Dashboard in your app editor.
2. Click Settings.
3. Next to App Template, click Submit Update.
4. Make your changes to the listing.
5. Click Submit Update to confirm.

You cannot submit another update while a previous one is still in review.

Managing your listings

From your app’s dashboard you can manage your template listing.

To manage a template listing:

1. Go to your app’s editor.
2. Click Dashboard.
3. Click Settings.
4. Click App Template.
5. Choose what you want to do:
   • See your app in the marketplace: Click the More Actions icon and click See on App Templates.
   • Remove your template from the marketplace: Click the More Actions icon and click Remove from App Templates.

FAQs

Click a question below to learn more.

• Can I still sell my templates?
• Can I see how many people used my template?
• Can I publish multiple templates?
• Where can I see all my template listings?
• If I remove my template listing, does it affect people who already used it?
• Can I share a template with only my workspace?
• What happens if my template has backend functions and secrets?
• What happens if my template uses paid third-party integrations or APIs?
• Can I limit the number of apps a user can create from my template?

Original source

How comments work

Comments live in your app editor’s preview. Each comment is pinned to the element you click and starts a thread where your collaborators can reply, react, and resolve.

Everyone who can edit the app sees the same comments, and new activity appears for all of you in real time. Comments stay anchored to their element as your app changes, so a thread you start today still points at the right spot after your next build.

Tip

Comments are only visible inside the app editor. People using your published app never see them.

To turn on comments, click the Comments icon at the top right of your app editor, next to your avatar.

Turn comments on and off from the top right of your app editor

Adding a comment

Add a comment by pointing at the exact element you want to talk about.

Writing your comment

Base44 captures a screenshot of the spot you click, and you can mention collaborators or add emoji as you write.

To add a comment:

1. Click the Comments icon to turn on comments.
2. Click the element you want to comment on. Base44 drops a pin and captures a screenshot of that part of the page.
3. Type your comment.
   • To mention a collaborator, type @ or click the Mention someone icon, then choose them from the list.
   • To include an emoji, click the Add emoji icon.
4. Click the send icon or press Enter to post it.

Write your comment on the element you clicked

Editing a comment

You can rewrite comments you posted yourself.

To edit a comment:

1. Open the thread and hover over your comment.
2. Click the More Actions icon and select Edit.
3. Change your text, then confirm.

Edit sits under the More Actions icon on your own comments

Editing the screenshot

If the captured screenshot doesn’t frame the right area, you can re-crop it on comments you created. Moving the frame also moves the comment’s pin to the element under it.

To edit a comment’s screenshot:

1. Open the thread, hover over the screenshot, and click Edit.
2. Drag the frame over the area you want to capture.
3. Click Save screenshot area.

The Edit button appears over the screenshot when you hover

Working with comment threads

A pin shows the avatars of everyone in the conversation. Click it to open the thread, or hover over it for a quick preview. In a thread you can:

• Reply: Continue the conversation under the original comment.
• React: Hover over a comment and click the Add reaction icon.
• Resolve: Click the More Actions icon and select Resolve to mark the thread as handled. Resolved threads leave the preview and the default list, and you can unresolve a thread to bring it back.
• Delete: Remove a reply you wrote, or select Delete thread under the More Actions icon to remove the entire thread. Deleting a thread removes it for everyone and can’t be undone.

A thread keeps the whole conversation in one place

Sending comments to the AI chat

Instead of handling feedback yourself, hand it to Base44. Sending a thread to the chat asks Base44 to read the comment, look at its screenshot, and act on it.

Tip

What happens when you send a comment:

• The thread appears in your chat as a comment card that tracks its status live, and you can click View thread on the card to jump back to the comment.
• Base44 adds a 👀 reaction to the comment while it works. If the comment asks a question, Base44 answers inside the thread without changing your app. If it asks for a change, Base44 builds it and replies in the thread when it’s done.
• Sending a comment doesn’t resolve it, so you decide when the thread is closed.

Sending a comment

You can hand a single thread to Base44 right from the comment.

To send a comment to the chat, do one of the following:

• Mention @Base44 in a comment or reply.
• Open the thread and click the Send to chat icon.

Sending several comments

You can send up to 20 threads to the chat as a single request, and Base44 works through them one by one.

To send a batch of threads:

1. In the comments panel, click the More Actions icon and select Send to chat.
2. Select the threads you want to include, or check Select all threads.
3. Click Send threads. The button shows how many threads you selected.

Browsing all comments

The comments panel collects every thread across your app, so nothing gets lost between pages.

When comments are turned on, a sidebar sits along the right edge of the preview, showing the people who commented. Hover over the sidebar to open the panel, where you can:

• Search: Find comments by their text or author.
• Filter: Click the filter icon to show only comments on the Current page, or only Unread ones.
• Resolve: Hover over a comment and click the Resolve icon to close its thread without opening it.
• Show resolved: Click the More Actions icon and turn on Show resolved to see handled threads, or select Mark all as read to clear your unread indicators.
• Jump to a comment: Click any comment to open its pin, even when it lives on another page.

Tip

A dot on the Comments icon means there’s activity you haven’t read yet.

FAQs

Here are answers to common questions about comments.

Original source