Settings & Home
In the Settings and Home tabs you control the basic behavior of the module and which Guard Service sections appear on the home screen.
Settings
Section titled “Settings”Branch protection
Section titled “Branch protection”- What it does: when enabled, the user must re-authenticate with biometrics or a password to access the branches
- Options: on or off
- Effect: an authentication prompt appears when opening the branches page (
/guard-service/branches)
Selection style
Section titled “Selection style”- What it does: determines how the branch selection is shown
- Options:
- Dropdown – branch as a collapsible field
- List – branch as a clickable list
- Tiles – branch as large, visual tiles
- Effect: the look of the branch overview page changes
Info feed settings
Section titled “Info feed settings”- Maximum entries – how many incidents are shown in the info feed at most
- Enable tap – when active, the user can tap an incident in the info feed to see details
In the Home tab you define which Guard Service sections (home sections) are visible on the home screen. Each section has an on/off switch.
Available sections:
- Branches – quick access to the branch list (tile view)
- Documents – link to the Drive module for files
- Info feed – shows the latest incidents directly on the home screen
- Configurable: how many entries at most? Details visible on tap?
- Call widget – emergency/control-center button (see Call Widget)
💡 Plan the wizard structure: before creating incident types with many steps, consider which information is really needed. A maximum of 5–7 steps per type is a good guideline.
💡 Set up bilingual: if your team works in German and English, configure incident types, steps and completion actions in both languages. Optional, but recommended.
💡 Use branch-data blocks: with the Locations module you create a branch-data block per branch. Changes to phone/email then reflect everywhere automatically – no manual update needed.
💡 Filter the info feed: not all incident types need to be visible in the info feed. Hide routine reports and highlight only important incidents.
💡 Export PDF: at the end of a patrol-log entry, users can choose “Export PDF” and save the report directly as a file.
Can I edit an incident afterwards?
Section titled “Can I edit an incident afterwards?”Yes. Go to the info feed, select an incident and open the details. From there it can be edited or deleted (with admin permission).
What happens to scanned documents?
Section titled “What happens to scanned documents?”They are uploaded and stored together with the incident. You can open them later in the incident detail view as PDF.
Can branch protection be disabled?
Section titled “Can branch protection be disabled?”Yes. The protection is optional and set in the editor. Admins switch it on or off depending on their security requirements.
What is the difference between “incident type” and “step”?
Section titled “What is the difference between “incident type” and “step”?”An incident type is the category (e.g. “theft”). A step is a single question within the wizard for that type.
Can completion actions be stored?
Section titled “Can completion actions be stored?”No. Email, push and share are pure triggers and are not stored persistently. This is intentional.
Can I enter multiple email addresses?
Section titled “Can I enter multiple email addresses?”No. One address is possible per email action. Create several email completion actions or use a distribution alias.
Does the module work without the Locations module?
Section titled “Does the module work without the Locations module?”Yes. The Locations module is optional. Without it, branch-data blocks cannot be used, but all other functions work normally. Plain text/image/PDF blocks remain possible.
Why does my Drive mirror stay empty?
Section titled “Why does my Drive mirror stay empty?”The Google Drive folder must be set to “Anyone with the link”. Otherwise the Cloud Function cannot mirror the structure. See Drive Mirror.