OperationsCommander - https://opscom.wiki

System Configuration

Guide to System Settings

The System Settings feature provides administrators with comprehensive control over the core functionalities and behaviors of the application. Its primary purpose is to allow for the centralized configuration and fine-tuning of various components, including security protocols, parking modules, and payment 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. Hover over System Configuration and click System Settings to access the centralized configuration area.

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

  3. Hover your cursor over any specific menu item label to view a tooltip explaining exactly what that setting controls.

  4. Modify the required settings to align with your organizational workflows.

Visual Cues and Status Indicators

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 assistance with the configuration.

Best Practices and Considerations

    Configuring SAML SSO with OPSCOM

    The Configuring SAML SSO with OPSCOM feature simplifies user access by allowing them to securely authenticate using their existing, managed corporate accounts. Its primary purpose is to eliminate the need for separate usernames and passwords, significantly enhancing user convenience and overall system security through automated synchronization. This article is intended for OPS-COM administrators.

    Setup and Configuration

    Implementing Security Assertion Markup Language (SAML) requires coordination between your organization's Identity Provider (IdP) and OPS-COM as the Service Provider (SP).

    Single Sign-On (SSO) is a premium paid feature. You must have the setup and recurring fees negotiated with your Sales Representative before proceeding. You must also configure your baseline login sources prior to completing this setup.

    Admin Side:

    Configuring the Login Source

    1. Hover over System Configuration, hover over Users, and click Login Sources.

    2. Click the pencil icon to edit your previously created SSO login source.

    3. Fill out the Service Provider and Identity Provider fields detailed below.

    4. Click the Save Changes button to reveal the required configuration tabs.

    Service Provider Fields (OPS-COM)

    These fields define exactly how OPS-COM will interact with your Identity Provider.

    Identity Provider Fields (External SAML)

    You must input values from your external SAML system's metadata into OPS-COM. This typically includes the Identity Provider's Entity ID, Single Sign-On URL, and IdP x509 Certificate.

    The IdP x509 Certificate field must contain the specific certificate issued by your Identity Provider (e.g., the certificate embedded in Azure's Federation Metadata). Do not copy the OPS-COM SP certificate into this field. Entering the wrong certificate will cause validation to silently fail.

    Synchronization Tab Configuration

    1. Click the Synchronization tab.

    2. Enable the Auto Create/Update User checkbox to allow the system to automatically create or update user profiles upon their first SAML login.

    3. Map the user attributes from your SSO system directly to the corresponding fields in OPS-COM (e.g., mapping your IdP's "email" attribute to the OPS-COM email field).

    4. Click the Save Changes button.

    Do not rename your Login Source after users have been associated with it. The Login Source value is permanently stored against every user record created via SSO. Changing it will immediately lock out those users on their next attempt.

    Translations Tab Configuration

    1. Click the Translations tab.

    2. Customize the text displayed on the login button for the user portal to ensure the experience is localized for your specific audiences.

    User Side: End-users do not interact with the SAML setup. Once configured, they simply navigate to the User Portal and click the newly customized login button to seamlessly authenticate with their corporate credentials.

    Using this Feature

    Administrators interact with this feature primarily by establishing the initial metadata handshake and monitoring the system for synchronization errors.

    Exchanging Metadata

    To establish the connection, you must provide your Identity Provider with the OPS-COM Service Provider metadata.

    1. Click the Metadata tab to view your system's XML code and integration URL.

    2. Copy the live metadata URL (e.g., https://[your-domain]/auth/saml2/[ENTITY_ID]/metadata).

    3. Provide this live URL directly to your Identity Provider.

    We strongly recommend providing your Identity Provider with the live URL rather than a downloaded, static XML file. When an IdP pulls from a live URL, it automatically fetches fresh metadata, ensuring the integration stays current and bypasses strict expiration timestamps.

    Troubleshooting Synchronization

    If users encounter issues logging in, administrators should review the following common causes:

    Best Practices and Considerations

    Troubleshooting - Email Server Communication Errors

    This article outlines the process for identifying and resolving email server communication errors within the system. Its primary purpose is to help administrators fix incorrect or missing "From" and "Reply-to" email addresses so that automated system communications, such as password reset confirmations, are dispatched successfully. This guide is intended for OPS-COM administrators responsible for system configuration and troubleshooting.

    Setup and Configuration

    Resolving communication errors requires access to the global system settings.

    Admin Side: Administrators must have the appropriate system role permissions enabled to access the configuration menus and modify global email parameters.

    User Side: End-users cannot configure these settings. However, users typically surface these errors when attempting to trigger automated emails through portal actions, such as submitting a password reset request.

    Resolving the Error

    Administrators can use the following instructions to identify the root cause of the communication failure and apply the necessary email configurations to resolve it.

    Identifying a Communication Error

    When a user attempts an action that triggers an automated email (such as using the forgot password form), the system relies on predefined sender addresses. If these addresses are missing, the system will fail to send the message, and the user will see a popup stating that the system could not communicate with the email server. This error explicitly indicates that the system lacks a defined "From" or "Reply-to" address.

    preimage.png

    Fixing Communication Errors

    1. Hover over System Configuration and click System Settings.

    2. Navigate to the General System Settings tab.

    3. Locate the Reply-to Admin Email Address field.

    4. Enter a valid, active email address into this field to serve as the system's sender address for automated communications.

    5. Click Save to apply the configuration changes.

    6. Re-attempt the user action that previously triggered the error (e.g., submitting the forgot password form) to verify the issue is resolved.

    Communication errors are almost always symptomatic of missing or incorrectly configured email parameters. If a user reports an email delivery failure or a communication error popup, verifying your global email settings should always be your first troubleshooting step.

    Best Practices and Considerations

    Alarms System Settings

    The Alarms System Settings feature allows administrators to configure and manage automated system alerts. Its primary purpose is to notify administrative and field enforcement staff of critical information regarding specific users, vehicles, or general events, thereby improving operational awareness and security. This article is intended for OPS-COM administrators responsible for backend configuration and enforcement operations.

    Setup and Configuration

    This feature is a core administrative tool used to define the active alerts that trigger within the system and on field enforcement devices.

    Admin Side: Administrators must have the appropriate system role permissions enabled to access and configure these settings.

    1. Hover over System Configuration and click Alarms System Settings.

    2. Review the active alarm categories and select the specific type you wish to configure or manage.

    3. Save any modifications to ensure they immediately propagate to the database and sync with active handheld devices.

    Using this Feature

    Administrators can use this feature to categorize and manage three distinct types of system alarms.

    Available Alarm Types

    Alarms configured in the backend sync directly to the handheld units used by enforcement staff. When an officer searches a flagged plate or user profile, the Android device will prominently display the alert on the screen so the officer can take immediate action.

    Best Practices and Considerations

    Defining User Profile Settings

    The User Profile Settings feature enables administrators to customize the specific information collected from users on their profile forms. Its primary purpose is to allow organizations to tailor the registration experience by controlling the visibility and mandatory status of data fields, ensuring that all necessary information is captured efficiently. This article is intended for OPS-COM administrators responsible for system configuration and user management.

    Setup and Configuration

    This feature is a core administrative tool used to dictate the fields presented to users during registration and profile updates.

    Admin Side: Administrators must have the appropriate system role permissions enabled to access the global system settings menu and modify user profile requirements.

    User Side: The configurations applied here directly dictate the fields end-users see and must complete when creating or updating their portal accounts.

    Using this Feature

    Administrators can use the following instructions to navigate to the settings menu and manage the visibility of various user profile fields.

    Configuring Field States

    1. Hover over System Configuration and click System Settings.

    2. Click User Profile on the Manage System Settings screen.

    3. Select the desired display state for each available profile item from the provided list.

    Available Field States

    The state selected for each field is highlighted in black, with a checkmark indicating the active selection. Items can be set to one of three states:

    Customizing Profile Sections

    The settings page allows you to customize several specific categories of user information:

    By default, the username field is not editable by administrators. If your organization requires the ability to manually change user account names, you must contact support@ops-com.com to request that the Allow Username Edits setting be enabled for your environment.

    Text2ParkMe Configuration

    If your organization utilizes the Text2ParkMe module, a second tab will be available on the User Profile settings page. This tab allows you to configure additional details that end-users can enter, including specific credit card information fields.

    If any credit card information is entered by the user via the Text2ParkMe tab, the system automatically switches all other credit card information fields to a required state for that specific transaction to ensure payment processing succeeds.

    Best Practices and Considerations

    Account Creation Preferences

    The Account Creation Preferences feature allows administrators to choose between granting users immediate portal access or requiring explicit email verification upon registration. Its primary purpose is to balance user convenience with system security and data integrity by controlling the onboarding flow. This article is intended for OPS-COM administrators responsible for managing the user registration experience.

    Setup and Configuration

    This feature is a global system setting that immediately dictates the onboarding workflow for all new users.

    Admin Side: Administrators must have the appropriate system role permissions to access the configuration menus and modify the registration parameters.

    User Side: Depending on the configured preference, new users will either be logged in immediately after creating an account or prompted to check their email for a verification link before they can access the portal. For complete user-side documentation, please refer to the Registering as a User article.

    Using this Feature

    Administrators can use the following instructions to locate the registration setting and toggle the desired onboarding workflow.

    Configuring the Account Creation Flow

    1. Hover over System Configuration, click System Settings, and click the User Profile tab.

    2. Locate the Auto Login After Register setting.

    3. Enable the Auto Login After Register toggle to allow immediate login, or disable it to require email verification.

    Available Configuration States

    The Auto Login After Register setting has two distinct states, each with specific implications for user experience and system security:

    While immediate login reduces friction, requiring email verification establishes a reliable communication channel from day one. This is crucial for securely processing future password resets, executing account recovery procedures, and delivering important system notifications.

    Best Practices and Considerations

    Configuring Multi-Factor Authentication on the User Portal

    Multi-Factor Authentication (MFA) adds a crucial second layer of security to user accounts by requiring one-time passwords (OTPs) sent via email. Its primary purpose is to significantly enhance protection against unauthorized access to the system. This article is intended for OPS-COM administrators responsible for configuring global security settings and managing the user login experience.

    Setup and Configuration

    Implementing MFA involves administrator-side configuration within the system settings and customizing the associated email template.

    Admin Side Configuration

    One-time passwords will not be available on the user portal until enabled within the global settings.

    1. Hover over System Configuration and click System Settings.

    2. Navigate to the User Profile tab.

    3. Configure the Enable Multi-Factor Authentication setting to your desired state.

    If the MFA setting is not available for you to change, please have your primary administrator contact support@ops-com.com to have the feature enabled for your environment.

    Email Template Configuration

    The content of the one-time password email sent to users is defined within a dedicated email template.

    1. Hover over System Configuration, click Content & Designs, then Email Templates.

    2. Locate and click the One-Time Password Email Template to edit its contents.

    3. Define the message and insert any relevant organizational branding.

    4. Utilize the available shortcodes to insert the OTP details:

      • [one_time_password]: Inserts the randomly generated one-time password.

      • [one_time_password value="issued_at"]: Inserts the time the password was generated.

      • [one_time_password value="expires_at"]: Inserts the time the password expires.

    Using this Feature

    Administrators can use the ternary setting to flexibly control how MFA is implemented across the user portal, while users manage their individual settings from their profile.

    Available Configuration States

    The Enable Multi-Factor Authentication setting has three distinct states:

    User Management

    Users can enable and manage their one-time password settings directly from their security page. For detailed instructions on the user experience, please refer to the Multi-Factor Authentication - User Portal wiki article.

    The state of a user's one-time password verification is stored in the local storage of their session data. If a user clears their browser cache, or attempts to log in using a different web browser or device, the MFA verification will not persist and they will be forced to enter a new one-time password.

    Best Practices and Considerations

    Password and Security Settings

    The Password and Security Settings feature provides administrators with critical tools to enforce robust password policies and manage login security for all backend administrative accounts. Its primary purpose is to protect sensitive system data, prevent unauthorized access, and ensure organizational compliance with modern security standards. This article is intended for OPS-COM administrators responsible for managing backend system configuration and access security.

    Setup and Configuration

    This feature requires high-level administrative access to view and manage global security protocols.

    Admin Side: Administrators must have the appropriate system role permissions enabled to access the centralized system settings menu.

    1. Hover over System Configuration and click System Settings.

    2. Click Security to open the management window and view all available security configurations.

    User Side: This feature dictates backend administrative security and does not directly configure the end-user parking portal login policies.

    Using this Feature

    Administrators can use the configuration window to define various aspects of password management, strength requirements, and automated account lockout policies.

    Password Security Settings

    Password Strength Requirements

    These settings allow you to enforce complexity rules for all new administrator passwords:

    Admin Account Lockout Settings

    These settings provide an automated layer of security by locking an administrator out of their account after repeated incorrect password attempts:

    Several major security settings (such as Salted Password Hashing, password expiry, and lockouts) are visible to administrators but can only be changed by the OPS-COM Team. For modifications to these restricted, read-only settings, please contact support@ops-com.com.

    Best Practices and Considerations

    Uploading and Managing Files

    The Manage Files feature provides a centralized repository for all files used across your application, primarily focusing on images for user and admin dashboards. Its primary purpose is to allow administrators to easily upload, view, organize, and manipulate visual content to ensure consistent branding throughout the system. This article is intended for OPS-COM administrators responsible for managing system content and visual assets.

    Setup and Configuration

    This feature is a core administrative tool used to store and manage system-wide assets.

    Admin Side: Administrators must have the appropriate system role permissions enabled to access the configuration menus and modify system files.

    User Side: This file manager is strictly a backend administrative tool; however, the uploaded files (such as logos, banners, and permit images) are ultimately visible to end-users on the parking portal.

    Using this Feature

    Administrators can use the following instructions to navigate the file manager, upload new assets, manipulate existing files, and embed images directly onto custom pages.

    Accessing and Viewing Files

    1. Hover over System Configuration and click Manage Files.

    2. Select your preferred viewing layout from the interface:

      • Grid Mode: Displays a visual thumbnail preview of each image, which is highly useful for quickly identifying visual content.

      • Table Mode: Provides a detailed list view, displaying file names, sizes, and other relevant information.

    Adding Files to the Repository

    1. Click the Upload tool to open the file upload interface.

    2. Click Select files and choose the desired images from your local device.

    3. Click Submit to upload the files directly to your site's storage.

    Once an image is successfully uploaded, it cannot be moved to a different folder. To maintain proper organization, ensure you navigate to and open the intended destination folder before you upload the image.

    Managing Existing Files

    1. Right-click on a specific image or file to open a contextual menu.

    2. Click Download to save a copy of the file to your local device, Rename to change the file name, or Delete to permanently remove the file from the system.

    3. Click View on an image, then click the Cropping icon to open a tool that allows you to resize or adjust the visible dimensions to focus on a specific area.

    Adding Images to a Page

    1. Click Insert in the text editor toolbar when editing a custom page or content area.

    2. Select Image from the dropdown menu.

    3. Click the search folder icon next to the source field to open the file manager.

    4. Locate and double-click the specific image you wish to insert. The image will immediately be added to the page at the location of your cursor.

    Best Practices and Considerations

    Admin Dashboard Setup (Quick Start)

    The OPS-COM Dashboard is a fully customizable, widget-based analytics interface built directly into the admin portal. Its primary purpose is to allow administrators to create tailored data views, arrange widgets freely on a drag-and-drop grid, and configure specific metrics to monitor daily operations. This article is intended for OPS-COM administrators seeking a brief overview of dashboard capabilities.

    Setup and Configuration

    Configuring personal dashboards and setting up widget layouts requires specific backend access.

    Admin Side: Administrators must have the appropriate administrative permissions enabled within their user role to access, configure, and save dashboard layouts.

    Using this Feature

    Administrators can use the dashboard interface to construct personalized, real-time views of system data.

    Customizing the Dashboard

    1. Navigate to the main dashboard interface within the admin portal.

    2. Create multiple personal dashboards to separate different types of data.

    3. Arrange widgets freely on the provided drag-and-drop grid.

    4. Configure each widget individually to show exactly the data you need for your daily workflows.

    Dashboard layouts and widget configuration are fully documented in our comprehensive feature guide. For detailed instructions on available widgets, deep customization, and advanced layout options, please refer to the Using the OPSCOM-ARC System Dashboard & Widgets article.

    Best Practices and Considerations