System Settings

This guide explains all pages under Settings → System in Zegeba (release 4.12.0). You’ll enable modules, set global behavior for the app, manage security rules, and tune the look & feel.

Prereqs

• Admin access to the Zegeba Dashboard.
• A published app (so visual changes can be validated in a real client).

Open System Settings

From the dashboard, go to Settings (left rail gear) → System.

Forms — enable Forms in the app

• Toggle Enable Forms Module In App on/off.
• Click Save.

Activities — labels & assignment message

• Set Custom Activity Label (Singular/Plural) if you want different words than “Activity/Activities”.
• (Optional) Check Custom Activity Assignment Message to define text sent with assignments. You can reference parameters shown on the right (e.g., Activity URL, State, Google Play Page, App Store Page, Username, Server URL).
• Click Save.
  Screenshot label: Settings → System → Activities.

Context — enable the Context module

• Toggle Enable Context Module.
• Click Save.
  Screenshot label: Settings → System → Context.

Top Menu

• Default actions: enable/rename New Entry, New Activity, New Context for the main action button.
• Custom Main Action Buttons: add specific actions tied to a Folder/Template and give each a Display Name.
• Click Save.
  Note: A full how-to for custom actions lives in the separate article “Top Menu — Custom Main Action Buttons.”
  Screenshot label: Settings → System → Top Menu.

Whitelisting

• Click Request MySQL Whitelisting to start the allow-listing process for IP/database access.
  Screenshot label: Settings → System → Whitelisting.

Information

• Review Zegeba Dashboard Version, Branch, SHA, Build, and Timestamp for support and auditing.
  Screenshot label: Settings → System → Information.

Password Policy — enforce minimum strength

• Defaults (minimum 8+ chars, ≥1 number, ≥1 special) cannot be weakened. You may raise requirements using the fields Total characters, Uppercase, Lowercase, Numbers, Special characters.
• Click Save.
  Screenshot label: Settings → System → Password Policy.

Menu — app menu behavior

• Menu Default Closed: keep the app’s side menu collapsed on open.
• Show Adhoc Reporting: expose ad-hoc reporting if enabled for your tenant.
• Show Context: show the Context section in the app menu.
• Click Save.
  Screenshot label: Settings → System → Menu.

Get App — platform download links

• Use the App Store and Google Play buttons to obtain the mobile app.
  Screenshot label: Settings → System → Get App.

Appearance — global colors and component styling

A. Custom Styles in App
- Set Primary Color, Background, Top Bar (Background/Text), Side Bar (Background/Text), Foreground Element (Background/Text), Standard Text, and Popup (Background/Text/Button Color).
- Use Set Default Colors to revert to Zegeba defaults.
- Click Save.
Screenshot label: Settings → System → Appearance → Custom Styles in App.

B. App Appearance (Advanced Style Settings)
- Buttons & Inputs: configure Primary Button, Secondary Button, Call-to-action Button, and Input Field (background/text colors).
- Foreground Elements: set colors for Form Card, Activity Card, Form Answer Card, Context Card, Outbox Card, and Login Form.
- Icons: pick colors for Menu Item, Form Icon, Activity Icon, Folder Icon, Ad Hoc Icon, Outbox Icon.
- Misc: adjust Breadcrumb (Active/Passive link), Info Chip (BG/Text), Table Header (BG/Text), Tabs Bar (BG).
- Use Reset to discard unsaved changes. Finish with Save.
Screenshot labels: Settings → System → Appearance (multiple subsections).

Validation

• Confirm modules you intended are visible in the app (Forms, Activities, Context).
• Open the app and ensure menu behavior (collapsed/expanded) matches your Menu settings.
• Attempt to set a weak password; verify it’s rejected per Password Policy.
• Review one screen that uses each color set (e.g., a form card, a table header, a CTA button) to check contrast and readability.
• Confirm build/version under Information matches what you expect to deploy.

Next

• See the companion article: Top Menu — Custom Main Action Buttons (for adding tailored actions like “Service” from a specific template).
• Continue with branding guidelines to standardize color usage across templates.

FAQs

1) What do the toggles in Forms/Activities/Context actually do?
They enable or disable each module in the Zegeba app for all users on the server. If a module is off, its features and menu entries are hidden.

2) Can I make passwords less strict than the defaults?
No. The default baseline (8+ characters with at least 1 number and 1 special character) cannot be weakened. You can only increase requirements.

3) What’s the difference between Custom Styles in App and App Appearance (Advanced)?
Custom Styles sets the core theme colors used broadly across the app. App Appearance provides fine-grained overrides for specific UI components (buttons, cards, icons, breadcrumbs, etc.).

4) Do appearance changes apply instantly to users?
Changes are server-wide after you Save. Users may need to refresh/restart the app session to see new colors.

5) Where do I find my current version/build to share with support?
Go to Settings → System → Information. You’ll see Zegeba Dashboard Version (e.g., 4.12.0), branch, commit (SHA) and build number.

6) How do I add a custom main action (e.g., “Service”)?
Open Settings → System → Top Menu, use Custom Main Action Buttons, pick an Action (e.g., New Activity), choose the Folder/Template, give it a Display Name, then Save. For full details, see the separate Top Menu article.

7) Can I preview appearance changes safely?
Use a non-production server or a staging app build. Apply colors, review them with a test user, and only then repeat the steps on production.

Article ID: 291