Application

Application page is where one can find information about their application and can update their application. Application page can be utilized to modify settings that are specific to the web application. The screen is available through pressing Edit on the Designer Home Page. Application page includes several sections:

Access Type

The Access Type setting defines how users can access your application. You can choose from three options:

• Require Authorization: Only authenticated and registered users can access the application.
• Allow Anonymous with API Authentication: Users can access the application without logging in, but API calls still require authentication.
• Allow Anonymous: The application is fully open and accessible to anyone with the link, without any authentication requirements.

These settings allow you to control the level of security and user access based on your application’s needs

Settings

This section lets users edit existing settings of the designer application.

Update the workbook

Use this section to replace the workbook model used by the current application transaction. For an Excel application, select or drag an updated .xlsx file into the Spreadsheet File drop zone. Select Update at the end of the page after choosing the revised workbook. SpreadsheetWeb runs the Workbook Compatibility Checker to compare the updated model with the existing user interface, database, and page design. Review missing or resized named ranges before continuing.

Updating the workbook in design mode does not change the published application until the transaction is published. The current transaction and its Preview use the updated workbook, while the live application continues to use the previously published calculation model.

Applications connected to Google Sheets can also use automatic workbook updates on a daily, weekly, or monthly schedule. Scheduled updates are compatibility-checked, preserve active work in progress, and provide notification and recent-history options.

User Interface Settings

Colors

Designer applications can be configured to use different color sets in visualizations, i.e. charts, and maps. The desired color set can be set by clicking Edit Default Colors button. Color manager window will allow to select a color set from the pre-defined sets. Also, a desired color set can be chosen too.

Culture

Designer applications support different Culture settings which can be used to set how the thousands and decimal separators will be shown.

Prompt User Confirmation on Log Out

Enabling this feature will ask for a confirmation from the user before logging out of the application. By using this feature, users can reduce the risk of logging out from the application with unsaved data.

Display Column Parsing Failures During Save

By default, parsing failure warnings are disabled. However, once enabled, users will be able to view parsing failure messages during the save process. These warnings help identify issues with data formatting that occur during parsing.

Show User Message When Accessing Application

This feature allows users to see who has entered the application in both the preview and published versions. If a user is logged in, their name will be displayed. If the user is not logged in, the entry will be marked as “unauthenticated.”

Use Tab Based Loading

This feature will be the default for newly-created applications, and minimizes the amount of initial loading needs to be done in the user interface at runtime. Large applications with many pages, controls, and grids should benefit greatly from this feature, so ensure that you try it out by flipping the flag on the Edit Application page in the Designer.

Overwrite Background Color

To set a fixed background color in the current Designer, open Layout & Controls → Overview → Change app theme → Backgrounds, choose Solid color, and select the required Background color. Select Save app theme to apply the choice to the draft.

Earlier interfaces call this setting Overwrite Background Color. The current dialog also offers gallery artwork, the theme default, and an uploaded image. See Application Backgrounds for all options.

Input Control Color

This feature applies the selected background color to all relevant input fields. An additional option is available to extend the same color to input cells within all input grids.

User Interface Version

This configuration determines which User Interface rendering version the application uses. All newly created applications run on Version 2, while older, legacy applications remain on Version 1 for compatibility.

Version 2 provides enhanced UI customization capabilities, allowing you to enforce consistent styling across the entire application. With this version, you can centrally manage global font sizes, theme colors, and skin selections, resulting in a more uniform, modern, and visually cohesive user experience.

Application appearance

The current Application theme dialog brings together Theme, Backgrounds, Fonts, and Charts & inputs. Open it from Layout & Controls → Overview → Change app theme.

In Backgrounds, choose built-in static or dynamic artwork, a solid color, the theme default, or an uploaded image. Gallery artwork supports semantic accents and adapts to theme changes. Animated artwork depends on plan eligibility and respects reduced-motion preferences.

The backdrop applies across the application. Use Save app theme, preview the affected pages, and publish the draft when ready. Follow Application Backgrounds for the complete procedure and current image-upload requirements.

Database Settings

This section allows you to configure database settings for your application, if applicable. By default, all new applications use the Simple Database model, which automatically captures data from all user interface controls in a generic JSON format. This model does not require any database design.

For applications that need more advanced or granular database functionality, you may switch to the Advanced Database model by selecting Convert to Advanced Database. Please note that this action is irreversible and will permanently delete all data currently stored in the existing database.

Enable Auto-Save

Auto-Save feature allows to save data periodically during the user session in case the user forgets to hit Save button manually. To be able to see and use the Auto-Save feature, you must have databases defined for your application and a save button present somewhere in your user interface. Enabling Auto-Save flag will make two additional options visible: Auto-Save Should Use Properties from Following Button and Auto-Save Interval.

The Auto-Save Should Use Properties from Following Button field is a dropdown, where you may select from the buttons that are present somewhere in your user interface. These buttons do not need to be visible or enabled to be selected. The purpose of this value is that the auto-save feature will mimic the usage of this button when performing the save action. This means you do not need to reconfigure all of the save-specific features, such as your tag saving behaviors or custom action triggers, to enable auto-save.

The Auto-Save Interval determines how often the auto-save should trigger. This measure is shown in hours (e.g., 01:00 would equate to once every hour, whereas 00:01 would be once per minute). This value is required for auto-save to function.

When a validation rule is triggered, SpreadsheetWeb prevents users from saving or submitting the application until the validation error is resolved. A custom error message is displayed, and users must correct the invalid data before they can proceed with saving or submitting. However, “if auto-save skips validation” is enabled, it does not adhere to validation rules in the same way as manual saves. Even when a validation error occurs, auto-save continues to function at the predefined intervals (e.g., every minute), allowing data to be saved automatically despite the presence of unresolved validation issues.

Enable Record Suggestion

There are cases where you may want the user to be prompted as to whether they would like to continue editing a record that they were previously working on the last time that they were in the particular application.

To accommodate this feature, we have enabled the Enabled Record Suggestions functionality. When a user creates or edits a record under an application, that information will be stored. The next time that the user enters the application without selecting a record from Data tab, the system will prompt them with a message, indicating that the last time they were here, they were editing a record, and ask whether they would like to return to continue editing that record.

This only works with authenticated users. If – for some reason – the record that the user was originally working on is no longer accessible to that user (e.g., the tags have changed, resulting in it no longer be accessible), then the user will not be prompted with the feature.

Enable Record Locking

If your designer application has Save Event, Enable Record Locking feature will help to lock a record to other users while another user is editing it.

Inactive Record Locking Timeout

If Enable Record Locking is enabled, this value can be set with following format “hh:mm”. Setting this value means that a record will be locked for the selected duration for other users but for the user which opened the record first.

Enable Google Analytics

SpreadsheetWeb also supports Google Analytics for Designer Applications. In order to use it, Enable Google Analytics checkbox needs to be to checked and the tracking ID must be entered into the Google Analytics Key input. A new tracking ID for the application can be retrieved by using the Google Analytics control panel. The domain address of the application should be entered correctly in order for Google Analytics to function as expected. After the application is saved and published, application’s hits from the Google Analytics tracking site can be monitored.

Fonts

This section allows you to update the font styles used throughout the entire application. You can modify the fonts for key text categories, Title, Subheading, Section Header, and Body, in a single place. Any changes you make here will be applied consistently across all pages and components, ensuring a unified and professional visual appearance.

Application Images

Upload Favicon

The Favicon allows users to modify the associated icon that shows up in the tab of the user’s browser. To upload a favicon, click on edit then select an image to upload or simply drag and drop your favicon into the drop zone. Once the file has been successfully uploaded, you can press the Upload button to save the favicon for your application.   PS: The permitted format for favicon images is *.ICO, which can be generated using a standard image and any number of web-based or desktop-based image editing tools.

Upload Branding Image

This feature allows users to modify the image that is displayed in the navigation bar of the application. To edit navigation bar branding, click on edit then select an image to upload or simply drag and drop an image into the drop zone. Once the file has been successfully uploaded, you can press the Upload button to save the navigation bar branding for your application.  PS: The permitted formats for branding images are *.PNG, *.JPEG, *.JPG, *.GIF, and *.SVG, which can be generated using a standard image and any number of web-based or desktop-based image editing tools.

Upload Background Image

In the current Designer, open Layout & Controls → Overview → Change app theme → Backgrounds → Uploaded image. Drag an image into the upload area or browse files, review the result and available layout options, then select Save app theme.

The current uploader accepts PNG, JPEG, or GIF files up to 8 MB. This replaces the older upload workflow described in earlier screenshots. The image is an application-wide backdrop; preview all affected pages before publishing. See Upload your own image for the full instructions.

SEO

The SEO section controls how a public application is described in search results and shared links. Introduced in the October 2026 release (26.10.0), it includes a page title, meta description, social-sharing information, indexing preferences, and Google Search Console verification.

SEO settings do not change who can access the application. Use Access Type to control whether users must sign in.

Open the SEO settings

1. Open your application in Designer and go to Settings.
2. Find the SEO section and turn on its switch. The label changes from SEO Disabled to SEO Enabled.
3. Use the Basics, Social, Indexing, and Search Console tabs to configure the application.

SEO settings save automatically to the draft. Publish the draft to update the live application's metadata. URL changes are an exception: selecting Update URL changes the application address immediately.

Page title and meta description

Open Basics to edit the text used to describe the application:

• Page title: Give the application a clear, descriptive title. This does not rename the application in Hub. Leave the field blank to use the application name. The counter recommends 60 characters and allows up to 500.
• Meta description: Summarize what people can do with the application. The counter recommends 160 characters.

Use Search under Previews to review the result as you edit. This is a representative preview: search engines may choose different text, omit an image, or select another page image.

Optional AI suggestions

The AI controls next to Page title and Meta description can help draft those values. Review and approve the context to be shared before generating a suggestion. Review the proposed wording and make any necessary edits before publishing. You can also write both fields yourself.

Social sharing

Open Social to configure link previews:

• Upload Open Graph image: Choose an image for shared links. The recommended size is 1200 × 630 pixels. Uploading here also updates the application image used by Hub.
• Reuse title and description for social sharing: Keep this selected to reuse the text from Basics, or clear it to enter separate social-sharing text.

Under Previews, select Social sharing to compare the approximate Facebook, LinkedIn, Bluesky, and X previews. Platforms may crop the image, shorten or omit text, and retain an older preview after you publish changes.

Indexing preferences

Open Indexing and choose whether to enable Allow search engines to index this application. After publishing, eligible public applications are included in the sitemap, which refreshes periodically. Search engines decide whether and when to crawl and list a page; enabling this setting does not guarantee indexing or ranking.

Turning indexing off does not make a public application private. Keep the application's access requirements configured separately through Access Type.

Google Search Console verification

Use Search Console to verify the application URL with Google:

1. In Google Search Console, add the application's complete public URL as a URL-prefix property.
2. Choose the HTML tag verification method and copy only the tag's content value, not the complete HTML tag.
3. In Designer, open SEO > Search Console and paste that value into Google verification token.
4. Publish the draft, then return to Google Search Console and complete verification.

This verifies the application's URL prefix, not every application hosted on the same domain. Changing the application's URL slug may require a new Search Console property.

Application URL

The URL slug field in Basics sets the last part of the public application address. Enter a revised slug and select Update URL to change it. Spaces and unsupported characters are replaced, and a suffix is added if the address is already taken.

Updating the URL takes effect immediately and also changes the application URL in Hub. Plan this separately from metadata edits, and review any existing links, embeds, or integrations that use the previous address.

Publish and verify

Review the Search and Social sharing previews, then publish the draft to apply the metadata to the live application. Open the published URL to check the result. Search engines and social platforms may take time to refresh their stored descriptions and previews.