# System Configuration # Roles and Permissions ## Roles and Permissions There are three menu options under the **System Configuration** -> **Admin Management** menu; **Manage Roles, Manage Groups** and **Edit Admin Users**. Click the **Manage Roles** button to begin. [](https://opscom.wiki/uploads/images/gallery/2024-10/siLimage.png) The **Manage Administrator Roles** screen displays. The Primary Administrator role will be available to select. This role will allow you to create new Roles and assign them to other Admin Users. Click the **Add New Role** button. Enter the ***Role name*** and the ***description*** for that role. The description will become the rollover tool tip that displays when you mouse over the **Edit Role** button of an existing role. Click Save Role to save. [](https://opscom.wiki/uploads/images/gallery/2024-06/HfSimage.png) You can ***edit*** any role by clicking the **Edit Role** button. You can edit the ***Role Name*** and ***Description*** for any Role except Primary Admin. Click the **Permissions** button to edit the permissions for any role. The **Editing Permissions** screen will display. The number next to the icons across the top bar indicate how many permissions in that category have been selected. The icons mirror the OPS-COM menu. Click an icon to display the permissions in that category. [](https://opscom.wiki/uploads/images/gallery/2024-06/FVUimage.png) To select a permission, enable the check box next to that permission. Once you have gone through each icon and selected all the permissions that are required for the role, click **Save Permissions**. That role is now created. You can assign this role to one or more users. Click the **System Config** menu and select **Edit Admin Users**. The **Manage Administrator Users** screen displays. From this screen you can create a new user or edit an existing one by selecting the appropriate option from the dropdown list. Click **Retrieve** to display the user options below. [](https://opscom.wiki/uploads/images/gallery/2024-06/6Suimage.png) Add or confirm the User information on the left and select the roles to apply to that user on the right. You can add a comment for any relevant notes about the user. Click **Update User** when you are finished. # New Page # Permissions in OPS-COM
## User Management Permissions | |
---|---|
Permission Names | Description |
View Users | Allows the admin user to view, but not change, the users in the system. User Search functionality is enabled. |
Edit Users | Allows the admin user to edit users in the system including new User Registration. This should be used with the 'View Users' permission. - If 'View Users' is enabled, Admins can see the user history including Permits and Violations issued (but not the details) and any payments outstanding for this user. - If 'View Users' is not enabled, Admins can only use the User Registration portion and cannot search for existing users. |
Delete User Aliases | This permission allows users to Update User Aliases. It cannot be used without 'View Users' and 'Edit Users' turned on. |
Edit Vehicle Information | Allows Admin to update vehicles and view the vehicle's history. Admins can also do a Plate Search from the User Management menu. In addition, Admins can see the DNTT reports. |
Edit Forms | Allows Admins to create, update and view forms. |
View Forms | Allows Admins to view all forms and see the user-submitted entries of forms. Users cannot create or edit forms without the 'Edit Forms' permission. |
Clear Alarms on User Profile | Allows Admins the ability to update and clear alarms on the user's profile. This must be used with 'View Users' and 'Edit Users' permissions enabled. |
Send Bulk Email | Allows Admins to send email messages to various groups of Users. |
## Locker Permissions | |
---|---|
Permission Names | Description |
Building Areas | Allows the Admin user to view buildings and building areas and add buildings and building areas. You must use this with the 'View Lockers' permission. |
View Lockers | Allows the Admin to view lockers and look at locker history. As well the Admin can see lockers awaiting payment. |
Edit Locker Information | Allows users to edit the locker information. |
Allocate Lockers | Ability to allocate locker numbers to a building area. |
Edit Locker Allocations | Allows creation and editing of locker sales windows, allows Admin users to view active locker sales window |
Allocation Locker - Single | Admins are able to add new buildings and building areas, able to create and update certain lockers. You must have 'View Lockers' enabled to use this permission effectively. |
## Parking Permissions | |
---|---|
Permission Names | Description |
Pricing & Lot Administration | Allows Admins to create and edit lots. This permission will not work by itself. The Admin must also have the following permissions: - View Permits - Edit Permits - Allocate Permits - Edit Permit Allocations |
View Permits | This allows the Admin to view Permit records, do Permit Switches and to view waiting lists. |
Edit Permits | This allows the Admin to edit Permit details. This permission allows access to most functions that relate to permits. |
Allocate Permits | Grants the ability to allocate permits to different lots. This permission will also grant all privileges of the 'View Permits' permission. |
Edit Permit Allocations | Allows access to edit the Permit Allocation Sales Window and the Active Permit Sales Window. |
View Access Cards | Allows the Admin to view Access cards. This will not work without the 'View Permits' permission enabled as well. |
Edit Access Cards | Allows the Admin to edit Access cards. This will not work without the 'View Permits' permission enabled as well. |
Add Access Cards | Allows the Admin to add Access cards. This will not work without the 'View Permits' permission enabled as well. |
Prorate Permit Purchases | Allows the Admin to prorate permit purchases for the end user. This cannot be used without 'User Management' permissions and 'Edit Permits' enabled. |
Create Temp Permit Entries | Allows Admins to use the Parking Validation utility. Please note, |
## Violations Permissions | |
---|---|
Permission Names | Description |
View Violations | Allows the Admin to see information about violations including, basic user details and details of any payments. |
Edit Violations | Allows the Admin to search for violations. This permission requires 'View Violations' to see the details. |
Edit Violation ticket number | Grants the ability to edit a violation number if you also have the 'View Violations' permission. |
Display as Ticket Writer | Grants the ability to be a ticket writer on the Handheld or the Web if the Admin also has the 'Add New Violations'. |
Add New Violations | Allows the Admin to issue a violation. The Admin must have the 'Edit Vehicle Information' permission found in the User Management section. |
Grant Violation Appeals | Gives the ability to manage Appeals and grant them. The Admin must have the 'View Appeal Reports' permission as well. |
View Appeal Reports | Allows the Admin to view Appeal reports for different officers. Admins must also have the 'View Violations' and 'Edit Violations' permissions. |
Issue / View Violation Notices | Allows the Admin the ability to issue and View Violation Notices. |
Manage Collections | Grants the ability to manage the collections process for violations. |
View Violation Reports | Allows the Admin to view financial and statistical reports regarding violations. Admins must have the 'View Violations' permission as well. |
## Incident Permissions | |
---|---|
Permission Names | Description |
Add/Edit Contact History User Notes | Grants the Admin the ability to add / edit notes in contact history. You must have User Management permissions to use this since it is accessed through the user profile. |
Delete User Contact History Notes | Grants the Admin the ability to delete User notes in contact history. You must have User Management permissions to use this since it is accessed through the user profile. You must also have the 'Add/Edit Contact History User Notes' permission. |
View All Incidents | This is a master permission that grants the ability to view all Incidents. This permission is normally used for high-level Admins as it grants access to all information. |
Add Incidents | Allows the Admin to add incidents and have an incident reported on their behalf. |
Delete Incident | USE WITH CAUTION - This permission should only be added to a Primary Admin. If this is enabled the Admin can remove the incident and all related records and files where they are not used in other reports. There is a button on the incident to "Delete Incident". |
Open Incidents | Allows the Admin to open incidents that are closed. This requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
Edit Incidents | Grants the ability to edit Incidents. This requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
View Incidents - Self | Allows the Admin to view Incidents if they are listed as the reporter. |
Edit Task Notes on Incidents | Grants the ability to edit comments on Incident tasks. Requires the 'View all Incidents' permission. |
Edit Incident summaries | Allows the Admin to edit Incident Summaries. Requires the 'View all Incidents' permission. |
Incident Administrator | Grants the ability to view and edit incidents. This permission is normally used for high-level Admins. |
View/Edit Confidential Information | Allows the Admin to View/Edit Confidential Information on reported incidents. Requires the 'View all Incidents' permission. |
Be assigned Tasks Directly | Allows the Admin to be assigned as an investigator for an Incident. |
Edit Incident Tasks | Grants the ability to edit Incident Tasks. Requires the 'View all Incidents' permission. |
Close Incidents / Checklists | Grants the ability to close Incidents and Checklists. Requires the following permissions: - View all Incidents - Incident Administrator |
Assign Incident to Case Manager | Allows the Admin to Ability to assign a Case Manager to an Incident. Requires the 'View all Incidents' permission. |
Assign Incident To An Investigator | Allows the Admin to assign an Investigator to an Incident. Requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
Assign Incident To A Different Investigator | Allows the Admin to assign a different Investigator to an Incident. Requires the 'View all Incidents' permission. This permission is normally used for high-level Admins. |
Is Incident Case Manager | Allows the Admin to be listed as a Case Manager that can be assigned to an Incident. |
Is Incident Shift Manager | Allows the Admin to be listed as an Incident Shift Manager. This will require some other high-level permissions as required for the job. |
View Incidents Distribution Reports | Grants the ability to view the Incident Distribution Reports. |
View Incident Reports | Grants the ability to view all Incident Reports in OPS-COM. |
View Incident In-House Report | Grants the ability to view the Unpaid In-House Incident report. |
Export Incident Reports | Grants the ability to export the Recent Incidents Report and the Sub-location Report to Excel. |
## Dispatch Permissions | |
---|---|
Permission Names | Description |
View License Plate Alarms | Allows Admins to view License Plate alarms. |
Receive License Plate Alarms via email | Allows Admins to receive Plate Alarms via email if they also have subscribed to the Alarms list. |
View People Alarms | Allows Admins to view People alarms. |
Receive People Alarms via email | Allows Admins to receive People Alarms via email if they also have subscribed to the Alarms list. |
Add New Dispatch Logs | Grants the ability to add dispatch logs. |
Edit Dispatch Logs | Grants the ability to edit the Admin's own dispatch logs. |
Edit All Dispatch Logs | Grants the ability to edit the dispatch logs of other Admins. |
Open Dispatch Logs | Allows Admins to Open dispatch logs. |
View Dispatch Logs | Allows Admins to View dispatch logs and close log records. |
Add/Drop Dispatch Logs | Grants the ability to remove the association of a Dispatch Log with an incident. |
View Cameras | Allows the Admins to view Cameras, if this is configured with OPS-COM. |
## Payment Permissions | |
---|---|
Permission Names | Description |
Manage User Credit Cards | Grants the ability to add, remove and update credit cards from Users. |
View Payments | Grants the ability to view payments. Limited access to user information is also granted. |
Edit Payments | Allows the Admin to process payments. Admin must have the 'View Payments' permission. |
Change Payment Type | Allows the Admin to change the Payment Type of a payment. |
Drop Payments | Allows the Admin to drop payments. |
Mark Bulk Payments | Grants the ability to mark Bulk payments for bulk processing. |
Refund Payments | Grants the ability to refund payments, but not process. |
Process Refunds/Adjustments | Allows the Admin to process refunds and adjustments. |
## System Content Permissions | |
---|---|
Permission Names | Description |
View and Select Files | Grants the ability to view and select files for use in editors. Admins must have the 'Manage System Messages' permission as well. |
Manage Files | Allows the Admin to add and remove files for use with content editors. Admins must have the 'Manage System Messages' permission as well. |
Manage System Messages | Grants the ability to edit the email templates, home page messages, system messages, Temp Permit Text and Notice Literature. |
View History Search | Allows the Admin to view history searches if they also have the corresponding User Management permissions. |
Purge Old Data | Allows the Admin to purge Data older than 7 years. |
## System Configuration Permissions | |
---|---|
Permission Names | Description |
Manage Roles | Grants the ability to manage roles and permissions. This is typically the job of a Primary Admin only. |
Edit Administrators | Allows the Admin to edit other Admin user accounts and assign roles based on their job description. This requires 'Manage Roles' to function. This is typically the job of a Primary Admin only. |
Manage System Configuration | Grants the ability to edit the System Settings. This is typically the job of a Primary Admin only. |
Manage User Types and Departments | Allows the Admin to manage User Types and Departments. |
Manage Vehicle Configuration | Allows the Admin to setup the different Vehicles descriptions that are used in OPS-COM. |
Manage Permit Types and States | Allows Admins to manage the Zones, Groups, Common Lots and Permit States. This must be used the 'Edit Permits' permission. |
Manage Access Cards | Grants the ability to setup Access card options. |
Manage Barcodes | Allows the Admin to setup Barcode options. |
Manage Locations | Grants the ability to setup Locations options for use in OPS-COM. |
Manage Handhelds | Allows the Admin to manage settings stored in the Handheld Commons area |
Manage Violation Offence Types | Allows the Admin to manage ticket types and ticket offence items. |
Manage Alert Lists | Allows the Admin to setup alert and alarm email lists. |
Manage Distribution Configuration | Allows the Admin access the Distribution setup options. |
Manage Dispatch Configuration | Grants the ability to the Dispatch setup options. |
Manage Incident Configuration | Allows the Admin to configure the IncidentAdmin options. |
Manage Cameras | Grants the ability to Admin to access the Camera options. |
Reset Database | Allows the Admin to the reset their preview database for testing. |
Manage Duplicates | Grants the ability to resolve duplicates in the system. |
### General System Component | ||
---|---|---|
Setting Name | Definition | Notes |
Default Notification Email | The address you wish all notifications from OPS-COM be sent to | |
Organization Name: Website | Set the name of the Organization | |
Organization Name: Handheld | Set the name of the Organization that appears on the handheld | |
Country | Set the country where the system is located | |
Company Address | Set your primary street address here | |
Time zone | Set the time zone based on your closest major city | |
System Timeout | Set how long the system can be idle before timeout (can be up to 6 hours) | |
From Email | This address will be the return address that appears in emails sent from OPS-COM | |
Time offset (mins) | This represents your time offset from Greenwich mean time | |
Using daylight savings | Used to toggle whether or not you are subject to daylight savings time | |
System Timeout | Set length of time before the admin user is automatically logged out of OPS-COM | |
Run the Task Scheduler | Used to toggle whether or not your system uses the Task Scheduler | |
Template Editor | Choose between RAW HTML Editor and a WYSIWYG Visual Editor | |
Select how to show dates | Used to set the date format | |
### Alarms Component | ||
**Setting Name** | **Definition** | Notes |
Use Alarms System | Controls if the Client can use Alarms module | Admins can see, only OPS-COM Team can change. |
Alarm Duration | ||
Generic Alarm Append Threshold | Picklist that allows you to determine the type of alarm you want to issue, and what Action you want taken. In addition you choose the Dispatch Sub Category that should be associated with this Alarm. For example, People Alarms should generate a System Alert with a Sub-Category of Personal Safety Reports. | |
People Alarm Append Threshold | Same as above | |
Vehicle Alarm Append Threshold | ||
Stolen Device Append Threshold | ||
Email Address | Email Address that an alert is sent to | |
Generic Alarm | Same as above | |
People Alarm | ||
Plate Alarm | ||
### Collections Component | ||
**Setting Name** | **Definition** | Notes |
Days before CRC is eligible | Set the length of time before a ticket is sent to court | |
MTO Lookups on all records | Perform an MTO Lookup on all records even if a user profile exists | |
Include All Unpaid Violations | When Toggled on: Includes all unpaid Violations when sending violation notices When Toggled off: Only the violation in question will be included in the letter | |
Prevent Violation Payment | Prevents violations from being paid through OPS-COM if they have been sent to collections | |
Prevent Purchases | Prevents Users from making any permit purchases if this is enabled and a violation has been sent to collections | |
Send Letter To All | When Toggled on: Send collections letter to all users even if they have been emailed a copy | |
**Deposits Component** | ||
**Setting Name** | **Definition** | Notes |
Use Deposits | Toggle the use of deposits on or off | |
Enable Deposits For Permits | ||
### Forms Component | ||
**Setting Name** | **Definition** | Notes |
Default email for sending form entries | These settings are used to control the Forms Module | |
### Global Component | ||
Setting Name | Definition | Notes |
Email Image Header | Select an image to appear in the header of all emails | |
Default Site Logo | Select a logo that appears on the mobile app, Text2ParkMe and the QR code interface | |
Default Site Header | Select a background image that appears in the header of the mobile app, Text2ParkMe and the QR code interface | |
Disable nightly email notifications | Disable auto-emails during system maintenance | |
Symbol before the dollar value | Which currency symbol to use before a dollar value | Accommodates the English format of the dollar value $100.00 |
Symbol after currency value | Which currency symbol to use after a dollar value | Accommodates the French format of the dollar value 100,00$ |
### Handheld Device | ||
**Setting Name** | **Definition** | Notes |
**Network Communication Model** | Select Standard or Volley | |
**Setting Name** | **Definition** | Notes |
Usage Limit | ||
Enable Megdgate nightly script. | ||
### Lightweight Directory Access Protocol Component | ||
Setting Name | Definition | Notes |
Log Failed Attempts | ||
Use SSL | ||
Servers | ||
BaseDN | ||
Account Suffix | ||
LDAP username | ||
LDAP password | ||
Student Group Name | ||
Staff Group Name | ||
### Licensing Component | ||
Setting Name | Definition | Notes |
Permits per year | Indicate the number of permits eligible to be used yearly (Usage Limit) | |
Violations per year | Indicate the number of violations eligible to be written yearly (Usage Limit) | |
Temp Permits per year | Indicate the number of temp permits eligible to be used yearly (Usage Limit) | |
Number of Handhelds | Indicate the number of OPS-COM for Android Licenses to be used (Usage Limit) | |
Mobile PL8RDR Cameras | Indicate the number of Mobile Cameras in use by client | |
Static LPR Cameras | Indicate the number of Static Cameras in use by client | |
Lockers per year | Indicate the number of lockers eligible to be used yearly (Usage Limit) | |
Validation Records per year | Indicate the number of validation records eligible to be used yearly (Usage Limit) | |
Dispatch Logs per year | Indicate the number of dispatch logs eligible to be used yearly (Usage Limit) | |
Incidents per year | Indicate the number of incidents records eligible to be used yearly (Usage Limit) | |
### Lockers Component | ||
Setting Name | Definition | Notes |
Enable Lockers Module | Toggles the use of the Lockers Module | Admins can see, only OPS-COM Team can change. |
Tax % | Percentage of tax to charge for lockers | |
Map of Lockers | Used to enter a path to a diagram or map image | |
Receipt Reply To Address | Reply to address on receipts if only a locker was purchased | |
### **License Plate Recognition Component** | ||
**Setting Name** | **Definition** | **Notes** |
Possible plate prefixes | Indicates the prefix of what typical plate reads in your region start with. (ie: 123 for Numbers, ABC for Alpha Characters) | |
Using Mobile LPR | This checkbox will toggle on or off the use of the LPR functionality on handheld devices | |
### **Parking Component** | ||
**Setting Name** | **Definition** | **Notes** |
Validation deletion cutoff minutes | Indicate how long a validation record is editable by an admin before it is locked into the system | |
### Payments Component | ||
Setting Name | Definition | Notes |
Gateway Online | Toggle to set the status of your payment gateway (Online or Offline) | |
Invoice Number | An incremental number for invoices. This can be set the first time you want to issue them | |
EFT Settings | This is used if you are set up to accept EFT payments through OPS-COM. You must be set up by OPS-COM Team first, before you can change anything | Admins can see, only OPS-COM Team can change. |
### Permits Component | ||
Setting Name | Definition | Notes |
Receipt Reply To Address | Reply to address for receipts that contain permits | |
Multiple Plate Validator | Allow multiple plates in parking validator | |
Require Payment for Rollovers | If enabled, only permits that are paid for and processed can be rolled over | |
Show remaining permits | If enabled, the number of remaining permits in a lot will be shown to site users. e.g. "32 Remaining" If disabled, the number of remaining permits will be replaced with "On Sale" (which hides how many permits are left from users) | Screenshot: [](https://opscom.wiki/uploads/images/gallery/2024-06/F48image.png) |
Enable User Permit Printing | ||
Show Total Spots Taken | ||
Show Waiting List Rank | ||
Show Only Visible Lots | ||
Waitlist Email Managers | Enter the email address of the admin who will be managing the waitlists | |
Waitlist Reservation Duration | Enter a timeframe for how long a waitlist reservation will be held before being released | |
Receipt Reply To Address | ||
Allow Credit Card Processing | Allows credit card payments for rollovers | Admins can see, only OPS-COM Team can change. |
Personal Information on Permit Print | Include personal information on hang tag printing | |
Require Mailing Address | Require a mailing address to be completed fully to purchase permits | |
Show Permit Lots on Landing Page | Show parking permit lots on the landing page | |
Show Only Visible Lots | Only show lots with an active visibility flag to the end user | |
Show Waiting List Rank | Allow users to see their rank on the waiting list | |
Show Total Spots Taken | When being added to a waiting list, show the number of spots that exist within the lot | |
Enable User Permit Printing | Allow users to print their own permits, this requires you to have a permit PDF message under System Messaging to work | |
Map of Permit Areas | This is the image of your parking map | |
### Security Component | ||
Setting Name | Definition | Notes |
Hash and Salt | Enable the hashing of passwords. Once set, it should not be turned off | Admins can see, only OPS-COM Team can change. |
Require Password Update | Require password resets after an admin changes the password | Admins can see, only OPS-COM Team can change. |
Toggle Password Expiry | Enable the use of password expiry | Admins can see, only OPS-COM Team can change. |
Password Expiry in days | Number of days before administrator must change their password | |
Enable Password History | Prevent passwords from being reused up to X days | Admins can see, only OPS-COM Team can change. |
How long to remember old passwords | The number of days the system will remember old passwords to prevent re-use | |
Minimum password length | The minimum password length for administrator passwords | |
Enable password strength requirements | Used to set standards in password creation based on password security strength | Admins can see, only OPS-COM Team can change. |
Numerical Characters | The minimum number of numbers required | |
Lower Case Characters | The minimum number of lower cases needed | |
Upper Case Characters | The minimum number of upper cases needed | |
Non-Alpha Numeric | The minimum of a Non-Alpha required | |
Enable Admin Lockouts | Enable admin lockouts after X invalid attempts within Y minutes | Admins can see, only OPS-COM Team can change. |
Lockout after X Attempts | Sets the number of retries with a wrong password before the system will lock you out | |
Login attempt timeframe | Sets the timeframe for wrong entries. For example, if you fail 3 times within 5 minutes the system will lock out this admin | |
Lock the admin out for X minutes | Sets the length of time in minutes that the admin will be locked out. Set at 120 minutes would mean the admin would be locked out for 2 hours before another attempt at logging in would be allowed | |
### Third Party Component | ||
Setting Name | Definition | Notes |
Twilio Account Number | Admins can see, only OPS-COM Team can change. | |
Twilio Auth Token | Admins can see, only OPS-COM Team can change. | |
T2 API Last Successful Fetch | Admins can see, only OPS-COM Team can change. | |
### User Profile Component | ||
Setting Name | Definition | Notes |
Enable Public Registration | If disabled, the Admins control the new account registration. Existing users can log in, but no one can create a profile | |
Profile Field Visibility | This controls the fields for the User Profile page | |
Max Student Number Digits | The maximum number of digits allowed in a student number. This can be useful if your organization requires student numbers that follow a specific min and max count. | |
Min Student Number Digits | The minimum number of digits allowed in a student numbers. This can be useful if your organization requires student numbers that follow a specific min and max count. | |
Max Employee Number Digits | The maximum number of digits in an employee number. This can be useful if your organization requires employee numbers that follow a specific maximum digit count. | |
### Vehicles Component | ||
Enable VIN | Toggles the use of VIN on and off | Only seen and edited by OPS-COM Team |
Require Vehicle Year | If enabled will require the vehicle year when users are adding a new vehicle. | |
### Violations Component | ||
Setting Name | Definition | Notes |
Enable Violations Module | Toggles the Violations Module on or off, this effects the web application and handhelds If this is toggled off, clients can chalk vehicles but cannot issue violations | |
Hide Zero Dollar Fines | When enabled, this prevents $0.00 violations, that are not warnings, from being displayed on the user side. These violations will still show up on the Admin side and will show on the Report by Officer and the Violation Summary by Officer report | |
Days until due | Indicates the number of days from the issue date that a user has to pay a ticket before it becomes overdue | |
Include Random Pin on Handheld Tickets | Select this item if you wish your users to have the ability to pay violations OPS-COM Quick Pay/Guest Payments. The PIN number is required in order to pay OPS-COM Quick Pay/Guest Payments | Admins can see, only OPS-COM Team can change. |
Handheld Footer | This is the message that will be applied to the end of each ticket that gets printed from the handheld | This footer is for violations only. Admins have the ability to change these settings on their own. |
Clear Violation Payments | ||
Appeal days | Indicates the number of days a user has to launch an appeal | |
Enable OPS-COM Quick Pay/Guest Payments Payments for Violations | ||
Link Violations to users | When enabled allows violations to be the user instead of a vehicle | Admins can see, only OPS-COM Team can change. |
Appeal Notification Email | The admin email(s) the system will send notifications to for new appeal requests. Leave blank if you don't want to receive these emails. | |
Automated Notification Email | The system will send notifications to this email for automated violation reports like "send overdue violations". | |
The prefix to go in front of the ticket number | These characters will appear before the ticket number on the printed ticket | Admins can see, only OPS-COM Team can change. |
The next number for printing tickets from the web | Sets the next sequential number to be on tickets printed from the web tool | Admins can see, only OPS-COM Team can change. |
Show Driver's License on Tickets | When selected, shows License number and Province of issuance on ticket | |
Show Ticket # as barcode on ticket | When selected, will print a bar code representing the ticket number on the ticket |
Label | ##### The label field is how you will identify your email templates. |
---|---|
Type | ##### The type is an nonadjustable value that lets you know the type of the email template. |
Language | ##### This field contains two options that allow you to select between French or English. |
Layout | ##### Select the layout that surrounds your messaging, this allows you to have multiple different layouts for different email templates. These layouts include your email header, footer, and its styling. You can create or adjust email template layouts under **System Config → Email Headers & Footers.** |
Subject | ##### This is the subject of the message you wish to send under the current email template. |
HTML Content | ##### Here you will write the message your users will receive. You can insert images, shortcodes, and use the smart editor, to format your messages just like other word processors. |
Text Content | ##### This section is a simple text editor that does not offer the use of shortcodes or any formatting. This is simply for the message itself and not necessarily the |
Page Attributes | Short Description |
---|---|
**Title** | The **Title** of the page you wish to create, which will be the name displayed on the user navigation bar. |
**Path** | The path after the domain. i.e. **login*****/** → This is the home page* Changing this to **lockers/area/1** will display **login/lockers/area/1** as the URL for that page. |
**Visibility** | You can toggle the visibility of your pages which will make it so your users can't see the page anymore, but you can still edit it. |
**Language** | Use this to select between two language options for a specific page. Tomahawk currently supports **English** and **French**. |
**Layout** | You can select the layout of your page here. Usually, you will have the **Default Layout** selected. |
**Content** | Your content will be the text on the page you are currently editing. You can also use **Shortcodes** here to display a body of material or feature. For example, a user login form could be displayed on your homepage. |
Toggle On(Visible Page) | Toggled Off(Invisible Page) |
---|---|
Message Attributes | Description |
---|---|
**Title** | The title that will be displayed across the top of the **System Message** when users navigate to that page. |
**Identifier** | The identifier is used to know which page you want to display the message by using **Shortcodes**. |
**Visibility** | This section toggles the visibility of your page which will make it so your users may not see the page, but you can still edit it. |
**Language** | Select between two language options for a specific page. Tomahawk current supports **English** and **French**. |
**Content** | Content is what will display on the actual page. You may use **Shortcodes** here to view predefined static or interactive content. For example, a user login form could be displayed on your homepage. |
Toggle On(Visible) | Toggled Off(Invisible) |
---|---|
[](https://opscom.wiki/uploads/images/gallery/2024-06/XY6image.png) | [](https://opscom.wiki/uploads/images/gallery/2024-06/L2Himage.png) |
Message Attributes | Description |
---|---|
**Title** | The title that will be displayed across the top of the **System Message** when users navigate to that page. |
**Identifier** | The identifier is used to know which page you want to display the message by using **Shortcodes**. |
**Visibility** | This section toggles the visibility of your page which will make it so your users may not see the page, but you can still edit it. |
**Language** | Select between two language options for a specific page. OPS-COM currently supports **English** and **French**. |
**Content** | Content is what will display on the actual page. You may use **Shortcodes** here to view predefined static or interactive content. For example, a user login form could be displayed on your homepage. |
`/* Style properties of our page body, this affects the entire page. */` `body {` ` ``background``: ``black` `url``(/uploads/FILES/OC_TOMA/parking-deck.jpg) ``center` `center``;` ` ``background-``size``: cover;` ` ``background-attachment``: ``fixed``;` ` ``color``: ``#FFF``;` `}` `/* This changes the color property of --Find where these classes are used ` `.card, .modal, .list-group-item {` ` ``color``: ``#333``;` `}` |
`/* Below are all of the styles for our header slideshow at the top of each page. */` `/*--------------WORD BANK---------------` ` ``* ELEMENTS: Elements are the tags with '<>' around them such as and ` ``* We access them here by giving them a Class name or ID. ` ` ``* PROPERTIES: Properties are used to define certain styles to a class or ID.` ` ``* CLASS: Generally used to assign a style to a group of HTML elements but can be used on single elements as well.` ` ``* They are assigned within HTML elements like this: where MyClass would be your class name.` ` ``* ID's: Generally used to assign styles to a single element but can be used on multiple elements as well.` ` ``*` ` ``*--------------CLASSES-----------------` ` ``*` ` ``* To learn more about the CSS Position Property see: https://www.w3schools.com/cssref/pr_class_position.asp` ` ``* For more information on CSS Syntax and Selectors see: https://www.w3schools.com/css/css_syntax.asp` ` ``* It is not recommended to adjust with the position of elements unless you are sure about the changes being made. This can dramatically change how content is positioned. ` ` ``*/` `/* Class Names and Elements` ` ``* [.slideshow-header]: Container that contains our slides and overlay.` ` ``*` ` ``* Properties` ` ``* @position: Adjust the position of the slideshow-header. For more information see: https://www.w3schools.com/css/css_positioning.asp` ` ``*/` `.slideshow-header {` ` ``position``:``relative``;` `}` `/* Class Names and Elements ` ` ``* [.slideshow-header]: Container that contains our slides and overlay.` ` ``* [.slides]: Controls the style properties of the individual slides.` ` ``* ` ` ``* Properties ` ` ``* @z-index: Adjust the stack placement of the [.slideshow-header] and [.slides] along the Z axis.` ` ``* @position: Define the position of the page. ` ` ``* @top:Change in the position from the top of an element.` ` ``* @left: Change in the position from the left of an element.` ` ``* @right: Change in the position from the right of an element.` ` ``* @bottom: Change in the position from the bottom of an element.` ` ``* @display: Adjusts how the content is displayed on the page. See: https://developer.mozilla.org/en-US/docs/Web/CSS/display and https://www.w3schools.com/css/css_display_visibility.asp` ` ``* @align-items: Aligns the child elements of this PARENT element to be centered. For a visual example see: https://developer.mozilla.org/en-US/docs/Web/CSS/align-items` ` ``* @justify-content: Defines how the space disturbed around the child elements. For a visual example see: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content` ` ``*` ` ``* These are the style properties and values of the slideshow header and its individual slides.` ` ``*/` `.slideshow-header .slides {` ` ``z-index``: ``0``;` ` ``position``:``absolute``;` ` ``top``:``0px``;` ` ``left``:``0px``;` ` ``right``:``0px``;` ` ``bottom``:``0px``;` ` ``display``:flex;` ` ``align-items: ``center``;` ` ``justify-``content``: ``center``;` `}` `/* Class Names and Elements` ` ``* [.slideshow-header]: A container that contains our slides and overlay.` ` ``* [.overlay]:` ` ``*` ` ``* Properties` ` ``* @z-index: Used to layer elements. Elements with a higher z-index number will appear before elements that are lower.` ` ``* @position: Set the position property for the element. We recommend you do not adjust this property unless you have knowledge on how the changes will affect your page.` ` ``*` ` ``* These are the styles for the overlay, as well as additional properties for the slideshow-header.` ` ``*/` `.slideshow-header .overlay {` ` ``z-index``: ``1``;` ` ``position``:``relative``;` `}` `/*--------------ID'S---------------*/` `/* ID Names and Elements` ` ``* [#slideshow-header] is the container used to contain the images you have chosen for your header` ` ``*` ` ``* Properties` ` ``* @overflow:` ` ``* @opacity:` ` ``* @box-shadow: Create a box shadow for this element.` ` ``* EX: box-shadow: a, b, c, d(e, f, g, h); ` ` ``*/` `#slideshow-header {` ` ``overflow``: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/overflow` ` ``box-shadow: https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow` `}` ` ` `/* ID Names and Elements` ` ``* [#slideshow-header] is the container used to contain the images you have chosen for your header` ` ``*` ` ``* Properties` ` ``* @width: 100% width will take of 100% of that element.` ` ``* @position:` ` ``*/` `#slideshow-header > div {` ` ``width``:``100%``;` ` ``position``: ``absolute``;` `}` ` ` `/* ID Names and Elements` ` ``* [#slideshow-header]: is the container used to contain the images you have chosen for your header.` ` ``* [div]: Refers to our HTML elements. ` ` ``* [img]: Refers to our images in the slideshow. ` ` ``* ` ` ``* Properties` ` ``* @width: Defines the width of the images, divs and slideshow-header. A value of 100% will display the image across the entire page. ` ` ``*/` `#slideshow-header div img {` ` ``width``: ``100%``;` `}` |