--- url: >- https://docs.corbitaltech.dev/products/whatsmarksaas-bundle-mobile-app/configuration.md description: >- Every setting you need to configure in WhatsMark SaaS Bundle for the WhatsMark: Inbox, CRM & Bots mobile app: Mobile App settings, push notifications, plans, website requirements and workspace setup. --- # Configuration Guide This page lists **every setting** you need to configure on your WhatsMark SaaS Bundle website before the mobile app can be used. It also explains where to find each setting, what it does and whether you need to change it again later. Work through the sections in order. When you finish, use the checklist at the end to confirm that everything is ready. In this guide: * **Platform admin** means the person who owns and manages the whole WhatsMark SaaS Bundle website. * **Workspace** means one business account on your website. Each workspace has its own chats, contacts and team members. * **Workspace user** means the owner or a staff member of a workspace. Workspace users are the people who sign in to the app. \[\[toc]] ## Overview: What to Configure and Where | # | What | Where | Who | Required? | |---|---|---|---|---| | 1 | Website requirements | Your server | Platform admin | Required | | 2 | Enable mobile app | **System Settings → Mobile App** | Platform admin | Required | | 3 | Maintenance mode | **System Settings → Mobile App** | Platform admin | Optional | | 4 | Push notifications | **System Settings → Mobile App** | Platform admin | Optional | | 5 | Mobile App plan feature | **Plans** (plan editor) | Platform admin | Required | | 6 | Workspace setup | Workspace on the website | Workspace owner | Required | ## Before You Start Make sure: * You can sign in to the website as the platform admin. * Your admin account has permission to **edit system settings**. Without this permission, you can see the Mobile App page but the **Save Changes** button is not shown. ## Section 1: Website Requirements The app talks to your website over the internet. Some basic website features must work, or parts of the app will not work. | Requirement | Why the app needs it | |---|---| | **WhatsMark SaaS Bundle version 1.3.0 or later** | The mobile app settings and the connection the app uses were added in version 1.3.0. Older versions cannot connect to the app. | | **HTTPS (a valid SSL certificate)** | The app only connects to addresses that start with `https://`. If your website shows a security warning in the browser, the app cannot connect. | | **Cron job running** | A cron job is a scheduled task on your server that runs the website's background work. Push notifications are sent by this background work. If the cron job is not running, notifications are not sent. | | **Email sending working** | The app's **Forgot password?** screen sends a 6-digit code by email. New users also need to verify their email address before they can sign in. If your website cannot send emails, users cannot reset their password or verify their account. | **How to check:** open your website address in a browser on your phone. It should open with `https://` and with no security warning. Then send yourself a password reset email from the website and check that it arrives. You only need to check these once. Check them again if you move your website to a new server or change its address. ## Section 2: Enable the Mobile App This switch allows the app to connect to your website. 1. Sign in to the website as the platform admin. 2. Go to **System Settings → Mobile App**. 3. Turn on **Enable mobile app**. 4. Click **Save Changes**. **Enable mobile app** is turned on by default after you update to version 1.3.0. Check it anyway, in case it was turned off. If you turn **Enable mobile app** off, the app cannot connect to your website. Everyone who is using the app sees a **Mobile app unavailable** screen. The app opens again by itself when you turn the setting back on. You only need to do this once. ## Section 3: Maintenance Mode (Optional) Maintenance mode stops everyone from using the app for a short time and shows them your message. Use it, for example, while you update your website. 1. Go to **System Settings → Mobile App**. 2. Turn on **Maintenance mode**. 3. In **Maintenance message**, type the message you want users to see. For example: "The app is under maintenance. Please try again later." The message can be up to 255 characters long. 4. Click **Save Changes**. While maintenance mode is on, everyone using the app sees an **Under maintenance** screen with your message. When the work is finished, turn off **Maintenance mode** and click **Save Changes**. The app opens again by itself within about 30 seconds. ::: tip Keep maintenance mode off normally Maintenance mode should be turned **off** for normal use. Only turn it on when you need to block the app for a short time. ::: ## Section 4: Push Notifications (Optional) Push notifications alert users on their phone when: * A customer sends a **new message** in a chat they can see. * A chat is **assigned** to them. To send notifications, your website needs a **Firebase service account file**. Firebase is Google's service that delivers notifications to phones. The service account file is a key that allows your website to send notifications through Firebase. ::: warning Use the Firebase project of your app The service account file must come from the **same Firebase project** that your mobile app was built with. If the file comes from a different Firebase project, the app still works, but no notification ever arrives. If our team built and published a branded app for you, we give you the Firebase project details when we hand over the app. ::: ### Step 1: Download the service account file from Firebase 1. Open the [Firebase console](https://console.firebase.google.com) and open your app's Firebase project. 2. Go to **Project settings → Service accounts**. 3. Click **Generate new private key**. Firebase downloads a `.json` file to your computer. ### Step 2: Add the file to your website 1. On your website, go to **System Settings → Mobile App**. 2. Turn on **Push notifications**. 3. Open the downloaded `.json` file in a text editor, such as Notepad. 4. Copy **all** of the file's content. 5. Paste the content into the **Firebase service account (JSON)** box. 6. Click **Save Changes**. ### If you see an error when you save | Message | What it means | What to do | |---|---|---| | A message that the field is required | **Push notifications** is turned on, but the **Firebase service account (JSON)** box is empty. | Paste the content of the service account file. | | This is not a Firebase service account file (project_id, client_email and private_key are required). | The pasted text is not a complete service account file. You may have copied only part of it, or pasted a different Firebase file, such as `google-services.json`. | Copy the **whole** service account file again and paste it. | You only need to do this once. Do it again only if you create a new key in Firebase or move to a different Firebase project. ::: warning Keep this file private The service account file gives access to your Firebase project. Do not share it or post it anywhere public. ::: ### How users control their notifications After you turn on push notifications, each user chooses which notifications they get in the app under **More → Notifications**. See [Notifications](/products/whatsmarksaas-bundle-mobile-app/notifications.md). ## Section 5: Add the Mobile App Feature to Your Plans A workspace user can only sign in to the app when their workspace's plan includes the **Mobile App** feature. ::: warning The Mobile App feature is off on all existing plans When you update to version 1.3.0, the **Mobile App** feature is turned **off** on every plan you already have. No workspace can use the app until you turn the feature on for its plan. New plans also start with the feature turned off. ::: 1. In the website admin, go to **Plans** and open the plan you want to change. 2. Turn on the **Mobile App** feature. 3. Save the plan. Repeat these steps for every plan that should include the app. Workspaces on a plan without the feature see this message on the sign-in screen: **"Your plan doesn't include the mobile app. Upgrade it on the website."** The plan is checked every time the app talks to the website. If a workspace moves to a plan without the feature, or its plan ends, the app stops working for that workspace straight away. The workspace's users also stop getting push notifications. Check this setting again every time you create a new plan. ## Section 6: Workspace Setup (Workspace Owner) These settings are done by each workspace owner on the website, not by the platform admin. Share this section with your workspace owners. ### Connect WhatsApp The workspace's WhatsApp Business account is connected on the **website only**. It cannot be connected from inside the app. Until WhatsApp is connected, the **Inbox**, **Campaigns** and template screens in the app show a **Connect WhatsApp** card instead of their content. ### Keep the plan active The workspace needs an active plan or a trial that has not ended. Paused, cancelled and ended plans cannot use the app. ### Check each team member's account A team member can sign in to the app only when: * Their account is **active**. Deactivated users cannot sign in. * Their **email address is verified**. ### Set team roles The app follows the same roles and permissions as the website. For example, a staff member without access to campaigns does not see the **Campaigns** tab in the app. Set roles on the website. See [Team Roles and Permissions](/products/whatsmarksaas-bundle-mobile-app/team-permissions.md). ### Share the website address When a user opens the app for the first time, the app may ask for your website address, for example `https://app.yourcompany.com`. Give this address to your users so they can connect the app. If your app was built for your website only, users never see this screen. ## Things That Are Not Settings Some app rules are fixed and cannot be changed in the settings: * **One phone per user.** A user can be signed in on one phone at a time. If the same user signs in on a second phone, the first phone is signed out. * **Platform admin accounts cannot sign in to the app.** The app is for workspace users only. * **There is no sign-up form in the app.** Accounts are created on the website. The **Register** link in the app opens your website's sign-up page. ## Verify the Setup Use this checklist to confirm that everything is configured. **Platform admin:** * \[ ] The website runs version 1.3.0 or later. * \[ ] The website opens with `https://` and no security warning. * \[ ] The cron job is running. * \[ ] The website can send emails. * \[ ] **Enable mobile app** is on. * \[ ] **Maintenance mode** is off. * \[ ] **Push notifications** is on and the Firebase service account file is saved (if you use notifications). * \[ ] The **Mobile App** feature is on for every plan that should include the app. **Workspace owner:** * \[ ] WhatsApp is connected on the website. * \[ ] The plan or trial is active. * \[ ] Team members are active and have verified their email address. * \[ ] Team roles are set. **Final test:** 1. Install the app on a phone and sign in with a workspace user account. Do not use the platform admin account. 2. Check that the **Inbox** shows your chats. 3. From another phone, send a WhatsApp message to the workspace's WhatsApp number. A notification should appear on the first phone (if you turned on push notifications). If something does not work, see [Troubleshooting](/products/whatsmarksaas-bundle-mobile-app/troubleshooting.md). ## Next Step Install the app and open it. Continue with [Welcome and Connect Your Workspace](/products/whatsmarksaas-bundle-mobile-app/welcome-and-connect.md).