Guide to System Settings

The System Settings infeature OPSCOM provideprovides administrators with comprehensive control over the core functionalities and behaviors of theirthe application,application. primarilyIts impactingprimary purpose is to allow for the administrative side. This centralized configuration area allows forand fine-tuning of various components, fromincluding generalsecurity systemprotocols, parametersparking modules, and securitypayment protocols to specific module functionalities like parking, violations, and payments,processing, ensuring the system operates according to organizational needs. This article is intended for OPS-COM administrators responsible for managing backend system configurations.

Setup and Configuration

This feature is a core administrative tool that dictates global system behavior.

Admin Side: Administrators must have the Manage System Configuration permission enabled within their user role to view and edit the system settings.

Using this Feature

Administrators can use the following instructions to navigate the system settings and configure global application parameters.

Accessing System Settings

1. Click

   Hover over System Configuration, thenand click System Settings to access thisthe centralized configuration area.

2. Explore the menus.available Hoveringconfiguration menus to locate the specific module or parameter you wish to adjust.

3. Hover your cursor over any specific menu item willlabel explainto withview a tooltip explaining exactly what thisthat setting controls.

4. Settings in

   Modify the required settings to align with your organizational workflows.

Visual Cues and Status Indicators

• Blue Text: Settings displayed in a blue font are read-only to Admins.standard Onlyadministrators. These represent core system parameters that only a Tomahawk User can enable/disableenable this.or Fordisable.

  help
with
• this

  Tooltips: Hovering over setting names will display a helpful tooltip detailing the function and impact of that specific toggle or field.

If your organization requires a change to a setting displayed in blue text, please communicate your needs clearly and contact support@ops-com.com. for

Onlyassistance Admins that havewith the permission to Manage System Configuration, will see the System Settings. If they have that permission, they can edit any system setting available. configuration.

---

Best Practices &and Considerations

• Review Allall Settingssettings:: System settings are granular and cover many aspects of OPSCOM. Regularly review all components to ensure configurations align with your organization's current policies and operational needs. System settings are granular and cover many distinct aspects of the application.

• SecurityPrioritize Settingssecurity Firstsettings:: Prioritize the configuration of Securitythe security component settings (e.g., password expiry, strength requirements, admin lockouts) to maintain a robust security posture for your admin accounts. This includes strictly defining password expiry limits, strength requirements, and admin lockouts.

• EmailVerify Configurationemail configuration:: Ensure that all relevant email addresses (are correctly set up to guarantee timely system communications and alerts. Key fields to verify include the Default Notification Email, From Email, Appeal Notification Email, and Automated Notification Email)Email.

  are correctly set up to ensure timely system communications and alerts.

• TimeMaintain Zonetime Accuracyzone accuracy:: Correctly setting your Time zone and Time offset is criticalcritical. forThese configurations ensure the completely accurate timestamping of all system events, purchased permits, and issued violations.

• ImpactUnderstand the impact of Togglestoggles:: Be mindful that many settings are simple on/off toggles. Understand the full impact of enabling or disabling a module (e.g., "Enable Violations Module") or a specific feature before making changes. Be mindful that many settings act as simple on/off switches that can immediately alter system behavior and user visibility.

• TeamFoster Collaborationteam collaboration:: For settings that require OPSCOM Team access to change, communicate your needs clearly to support staff. For other settings, collaborateCollaborate with your internal teamsteams, (such as IT, finance, enforcement)and enforcement, to ensure changes meet everyone's operational requirements.

• Testing Changes: ForTest significant changes,changes: especiallyConsider thosetesting impactingsignificant changes in a preview environment before applying them to your live production system. This is highly recommended for settings that heavily impact user-side visibility or core workflows,workflows. considerFor testingdetailed insetup instructions, refer to the Create or Refresh a Preview Space, beforepage.

  applying to your live production system.