In this section · 7 articles

Core Mobile configuration settings

The 13 configuration sections on the Core Mobile dashboard, field by field, with which ones your app actually receives. Also the platform API key, and every Core Mobile permission.

Applies to
Core Mobile 2.0 and later
Who can do this
Platform owner, Developer
Where
Core Mobile › Dashboard (Platform Administration)
On this page

Open a section

  1. In the Platform Administration sidebar, select Core Mobile › Dashboard. The Dashboard shows the app's Environment, Maintenance, Feature flags and Active theme, then a tile for each section under Configurations.
  2. On a section's tile, select Configure. The section opens in a side panel.
  3. Change what you need, then select Save changes. You see, for example, "Release Control updated successfully."
Core Mobile Dashboard with the Release Control section open in a side panel, showing Android and iOS version fields and store URLs, with Save changes highlighted.

You only see the tiles you may view. A tile marked View only opens without Save changes.

Several sections start with example values, such as the app name Core Mobile and the company Laramin Inc. Replace them before your app goes live.

What reaches the app

SectionSent to the app
Branding Management, App Settings, Release Control, Localization, Maintenance ManagementYes, in the app's start-up settings.
Contact & SupportYes, except the social links.
API SecurityOnly the Platform API Key, which the app sends back to prove it's yours.
Theme Settings, API Configuration, Push Notifications, Analytics & Monitoring, Offline Experience, Device CapabilityNo. Core Mobile saves them, but no mobile answer includes them, so an app can't read them. Before Core 12.8, an app could read them through the older settings list, GET /api/v1/mobile/get_setting.

The theme the app receives comes from Core Mobile › Themes, not from Theme Settings. See Change the app's theme, remote settings and feature flags.

Branding Management

FieldWhat it does
App NameThe app's name. Required, up to 100 characters.
App Display Name, Short NameLonger and shorter versions of the name, for places with more or less room.
Company Name, Company Tagline, Company DescriptionYour business, as the app shows it.
Logo (Light), Logo (Dark), Horizontal Logo, Square Logo, Monochrome LogoLogo images for light and dark backgrounds and different shapes. The app receives their full addresses.
Branding Management side panel with the Identity group (App Name, App Display Name, Short Name), the Company group and the Logos group, each logo with Edit, Replace and Remove.

App Settings

FieldWhat it doesDefault
Maintenance ModeTells the app it's under maintenance.Off
Debug ModeTells the app to show extra information for developers.Off
EnvironmentProduction, Staging or Development.Production
Offline SupportTells the app it may work offline.On
App Settings side panel with Maintenance Mode and Debug Mode off, Environment set to Production and Offline Support on, at their default values.

The app also receives whether Allow mobile app sign-up is on in Core's Security settings. See Security settings.

Release Control

One set for Android and one for iOS, then Update Rules.

FieldWhat it does
Current Version, Minimum Version, Latest VersionVersions of the mobile app, such as 2.3.0, up to 20 characters. Starts at 1.0.0. Minimum Version is the oldest app that may still connect. Enter the app's version, not your Laramin's.
Play Store URL / App Store URLWhere the app sends people to update.
Force UpdateTells the app an update is required.
Soft UpdateTells the app to suggest an update.
Update MessageThe message the app shows with an update.
Release Control side panel with Android and iOS groups showing Current, Minimum and Latest Version and store URLs, and Update Rules with Force Update and Soft Update off and an Update Message.

The app decides what to do with Force Update, Soft Update and the Update Message. Minimum Version is also enforced by your Laramin: an older app that says its version is refused, and asked to update.

Saving refuses a Minimum Version higher than the platform's Latest Version (or its Current Version, when Latest Version is empty), because no installed app could meet it. You see The minimum app version … is higher than the latest app version … Enter the mobile app's version, not the server's.

Release Control side panel with Android Minimum Version 12.6.0 outlined in red and the error that it is higher than the latest app version (2.3.0), asking for the mobile app's version.

Localization

FieldWhat it doesDefault
Default Language, Fallback LanguageThe app's language, and the one used when text is missing. Chosen from the languages your Laramin publishes. If one stops being published, the app gets your Laramin's default language instead.English
Supported Languages, Active LanguagesThe languages the app offers. Leave them empty to offer every language your Laramin publishes, or choose some of those.Empty: every published language
Date Format, Time Format, Number Format, Currency FormatChosen from a list. The app receives the format patterns.
RTL SupportTells the app to support right-to-left languages.Off
Localization side panel with Default and Fallback Language set to English, Supported and Active Languages empty, the Date, Time, Number and Currency Format lists, and RTL Support off.

Saving refuses a language your Laramin doesn't publish: … is not a published language on this site, so the app cannot use it. Publish it in Languages first, or remove it. See Add a language.

If your Laramin had Core Mobile before version 2.1.0, Supported Languages and Active Languages may still hold only English, so the app offers English only. To offer every published language, clear both lists and select Save changes, or ask whoever runs your server to run php artisan coremobile:reset-seeded-languages --apply. That command clears a list only if it holds English alone.

Contact & Support

GroupFields
ContactName, Email, Phone, WhatsApp
SupportHelp Center URL, Knowledge Base URL, Ticket Portal URL
SocialFacebook, Instagram, LinkedIn, YouTube, X. Saved, not sent to the app.
Contact & Support side panel with Contact name, email, phone and WhatsApp filled in, three Support URLs, and empty Social fields for Facebook, Instagram, LinkedIn, YouTube and X.

Maintenance Management

FieldWhat it doesDefault
Maintenance ScopeNone, Global, Android Only or iOS Only.None
Start Time, End TimeThe maintenance window, in your Laramin's time zone. The app receives the times with the time zone, so every phone starts and ends maintenance at the same moment, wherever it is.
Maintenance MessageWhat the app shows."We are performing scheduled maintenance. Please check back shortly."
Maintenance Management side panel with Maintenance Scope set to None, empty Start Time and End Time fields, and a Maintenance Message telling users the app is down for planned work.

The app decides what to do with these values. To close your Laramin's API itself, see Turn on maintenance mode.

API Security

FieldWhat it doesDefault
Platform API KeyThe key apps send, as an X-Api-Key header or a bearer token, to read settings before anyone signs in. At least 24 characters. Stored encrypted and never shown again: leave the box empty to keep the current key.Empty
Generate new keyReplaces the key with a new random one when you save.
JWT Expiry (s), Refresh Expiry (s), API Key Rotation (days)Saved for reference.3600, 1209600, 90
Root Detection, Jailbreak Detection, Emulator Detection, Screenshot BlockingSaved for reference.Off
API Security side panel with a saved Platform API Key shown masked as leave blank to keep, Generate new key off, JWT Expiry 3600, Refresh Expiry 1209600, API Key Rotation 90 and all security flags off.

The Platform API Key isn't only for Core Mobile: it's the key your Laramin's whole API accepts from any app or program that isn't signed in. When it's empty, the server's PLATFORM_API_KEY setting is used. When both are empty, only signed-in requests are accepted, so an app can't load its settings before sign-in.

Careful: Changing the key stops every app and program that uses the old one, straight away, for anything it asks before someone signs in. People already signed in to the app stay signed in: from Core 12.8, keeping them signed in doesn't need the key. Core Mobile 2.1.0 never shows a key made with Generate new key: saving only says API Security updated successfully., and the form never displays the key. So nobody can give it to the app. Type your own long, random key instead, and keep a copy where your developers can reach it safely.

Sections that aren't sent to the app

SectionFieldsDefaults
Theme SettingsActive Variant, Font Family, Border Radius, Elevation, Animations, Shadow Configuration, Font Sizes (JSON), Font Weights (JSON), Line Heights (JSON)Light, Inter, 8, 2, on
API ConfigurationAPI Base URL, API Version, Timeout (s), Retry Count, Retry Delay (s), Polling Interval (s), Sync Frequency (s)empty, v1, 30, 3, 2, 60, 300
Push NotificationsFirebase Project ID, Firebase Sender ID, Firebase API Keyempty
Analytics & MonitoringFirebase Analytics, PostHog, PostHog Key, Mixpanel, Mixpanel Token, Crash Reporting, Performance Monitoring, User Consent Required, Tracking Enabledall off except User Consent Required
Offline ExperienceCache Duration (s), Sync Interval (s), Retry Count, Offline Banner Message3600, 900, 3
Device CapabilityGPS, Camera, NFC, Bluetooth, Microphone, Required Permissions, Optional Permissionsall off
The Push Notifications side panel, with empty Firebase Project ID, Firebase Sender ID and Firebase API Key boxes, and Cancel and Save changes at the bottom.

Permissions

Each configuration section has a pair of permissions, feature.cm.<section>.view and feature.cm.<section>.edit, labeled View and Manage, for example View Release Control and Manage Release Control:

Section<section>
The Dashboard itselfdashboard (View Mobile Dashboard)
Branding Management, App Settings, Release Control, Localizationbranding, app, release, localization
API Configuration, API Security, Push Notificationsapi, security, push
Contact & Support, Analytics & Monitoring, Maintenance Managementcontact, analytics, maintenance
Offline Experience, Device Capabilityoffline, device
Theme Settingstheme, shared with Themes below

The other screens each have seven permissions, feature.cm.<resource>.list, .view, .create, .edit, .delete, .restore and .remove, labeled List, View, Create, Edit, Soft Delete, Restore and Force Delete:

Screen<resource>Covers
ThemesthemeThemes
Remote Configuration, Feature Flagsremote_configBoth screens
Mobile Experience RulesrulesRules
AudiencesaudienceAudiences
OnboardingonboardingFlows and their slides
NavigationnavMenus and their items
App Dashboardsmobile_dashboardDashboards and their widgets

In the role editor, they're under five groups: Mobile Branding, Theme & Localization, Mobile App, Release & Device, Mobile API, Security & Push, Remote Config & Experience Rules and Mobile Analytics, Maintenance & Support. To give them, see Give someone a role.

Careful: Manage API Security lets someone change the key every app uses to reach your Laramin. Give it only to people who look after your apps.