This section deals with managing Franchise Context Settings for the following:
Note: Admins can access Settings by clicking on the Manage menu drop down.
User
Password Reset Interval
As the title implies, here is where you set your global password reset policy. What this does, if set to anything but 'Passwords never expire,' will reset all Users in the respective Franchise Context by sending out a tokenized email to each and every active User asking them to reset their passwords; according, of course, to the set reset interval. It will also prevent the Users from logging in with their old passwords. This is a precaution that can help guard against unknown/unauthorized system access, if suspected or detected.
Profile Links
These links will show up on User's profiles. They can be anything the Franchise Context Admin wants them to be. They could be links to other Franchise Specific resources that Admins may want to share with Clients, or they could be links to third-party online payroll services for Franchise staff. Anything goes here. Facebook Pages or Twitter accounts for local franchises come to mind as well. The links have a Title and an actual Link field followed by a View Rights setting. Those are as follows:
- Internal - Available to all Users but Clients
- External - Available to JUST Clients
Inteliguide Usage Disclaimer/Agreement
This is a single multi-line text field that Franchise Admins can use to add whatever usage agreement they or their lawyers deem prudent. It could really be anything they desire. This is more for liability purposes, but could be anything you like! Users will be confronted with this along with a check box they have to check acknowledging acceptance of the agreement when they newly log in after their User Account is created.
Shift Commitments: Double Booking Flexibility
This section modifies the default shift conflict commitment restrictions
Shift Notifications: Alerts, Reminders, & Updates
This same section is found in the Profile Edit Form, but those settings there apply to the individual Users that decide to set them. Enabling any of the Shift Notifications here in User Settings will allow each respective Personal Shift Notification Setting to optionally be disabled (at each User's discretion). When enabled, these DO NOT override any Personal Settings. When disabled, they DO override Personal Settings.
- Shift Commitments (when Users either Commit themselves to Shifts, or when management Schedules them directly)
- Shift Reminders (up to two reminders can be sent out to Users per Scheduled Shift depending on how far out into the future the Scheduled Shift is)
- Shift Updates (when Shifts are modified before they're due to be worked)
Checking or unchecking specific Shift Notifications will turn on or off those respective notifications. Admins cannot go into other User's Profiles and adjust these settings for them. Every User can only access their own Profile. That's why we've added this section under the overall app User Settings, as a measure to individually turn on or off app-wide Shift Notifications.
Note: If Shift Reminders are disabled, it will take a while for the old Scheduled reminders to work their way out of the system. Every time a new Shift is Scheduled in any way for a User, the reminders are Scheduled accordingly. Unchecking the Shift Reminders option will prevent any new ones from being enqueued.
Payroll
Interval Start Date/Time & Overtime
This is where you can set the frequency of your payroll. Right now Inteliguide allows for Weekly or Biweekly. You can choose the start Date/Time of your payroll, and payroll cycles will occur depending on your Interval setting from there on out.
- Interval
- Biweekly (typical every two weeks)
- Weekly
- Start Date/Time (separate fields)
- Overtime
Right now, Inteliguide only allows one overtime calculation type: the standard 40 hour work week. That overtime is only calculated on W-2 User Types. We are planning on adding more extensive rules to account for variances state-by-state. Coming soon!
Paid Holidays Multiplier & Date Collection
Define a multiplier and add days that qualify as Paid Holidays. Those days will apply the multiplier to any Shifts spanning into, out of, or wholly contained within them. The math is done for you on partial and whole Holiday Shifts alike!
Auto Send Reports
This allows you to enable an email report that will be sent at the close of every payroll cycle, which varies depending on your interval settings. If enabled, you can set the report type you'd like to receive:
- Normal (summaries)
- Detailed (line item list of every Shift for every User)
You can choose to add one or many Admin Users as Payroll Report recipients.
Customize Employee Type Codes for Report.csv
This will determine how the Employee Types are displayed in the csv file version of the Payroll Report. Some payroll providers have specific values that they anticipate, and these settings make the generated file a little more flexible.
Customize Pay Codes for Payroll Export
The values for:
- 1099 Pay
- Salary Pay
- Regular Pay
- Overtime Pay
- Holiday Regular Pay
- Holiday Overtime Pay
Can all be customized and will appear for their respective line items in the Payroll CSV Export report (which can be toggled on when generating Payrolls)
Payroll Toggles for Page Load & Auto Send Defaults
Setting these checkboxes will determine which toggles are selected when Payroll first loads upon navigating to it through the REPORTS Main Navigation Tab. These toggles will also be affect the output of the reports that get sent automatically at the close of each period.
Time Punch Flexibility
These settings let Admins restrict User input Clock In values via the Dash or Mobile within a certain time frame before and/or after a Shift Start/End Date/Time. For example, if Admins save 15 into "Minutes Before Clock In" field... User initiated Clock In attempts 20 minutes before the Shift Start Date/Time will be rejected.
So the example goes, if a value of 10 were saved in the "Minutes After Clock Out" field, User initiated Clock Out attempts exceeding 10 minutes after the Shift End Date/Time will be rejected.
Enter integer values for these fields:
- Minutes Before Clock In
- Minutes After Clock Out
Note: Rejected Clock Out attempts will require Users to follow up with their managers/supervisors in order to correct. Leaving the values empty lifts any User initiated Clock In/Out restrictions. Also, these settings are used to determine how long a Civilian or Cop User can edit their Activity Reports after their Shift ends if they haven't already Clocked Out. They follow the same restrictions for Time Punches, but, in effect, impose no restrictions if left empty.
Geofence Flexibility
Your set radius here will determine if officers are close enough to make a Time Punch (Clock/Lunch In/Out) during their Shift. If the officer is within the defined Geofence, and they've allowed the app or browser access to their gps location on their smart device (a good idea for accountability reasons), they'll need to be within the set distance in order to make a Time Punch.
This assumes that their work Location or all their work Locations have been added to any Group Shift (a Shift created for a Group of Locations instead of just a single Location) they're working and are geolocated correctly; meaning the address has been resolved to an accurate or semi-accurate translation in long lat values. You can double check that via the Locations/Groups Detail pages.
Finally, the checkbox for the Group option is to allow Admins to bypass the Geofence option for Shifts made for Groups. This is for cases where officers are starting patrols and Clocking In from their houses, instead of from any given work Location. This prevents the need in those cases for Admins to be forced to add employee locations to Inteliguide. The drawback there is, officers can clock in from anywhere, so Admins would need to be able to trust their patrol staff to do what's right.
Management Alerts: Late & No-Show
We released Site Managers to help delegate administrative tasks without giving away full Admin rights to the system. As part of that, we intended to give more time & attendance visibility to those that are now able to manage pools of Locations. That's why we've added a new way of monitoring the punctuality of officers Clocking In to Shifts. Alternatively, you can also assign any Manager User, and that User will be a recipient for all Late & No-Show Alerts regardless of Location.
Admins can find the new Settings under Manage -> Settings -> Payroll. We've added a new section there for Management Alerts: Late & No-Show with the following options:
- Alert on Late Punch (If the User is Late to Clock Into a Shift, and they still complete the Clock In… this alert will go out)
- Alert on Late or No-Show (If the User is Late, this alert will go out. It will ALSO go out if the User doesn't Clock In at all during their Shift)
- Alert Threshold
- 5
- 10
- 15
- 20
- 25
- 30
- Recipients
- Site Managers (will delegate Alerts to Site Managers based on what Locations have been assigned to their Accounts. Any Shift created for a Location or Group containing at least one of their assigned Locations will be monitoring for Late and No-Show activity)
- List of Active Manager Users (all Active Users other than Clients, Cops, and Civilians. If any of these are selected, they will be considered recipients for ALL Alerts for ALL Locations)
Note: Unless a User actively initiates a Clock In, we have no event to determine if there's a Late or No-Show Alert needing to go out. So we have to poll constantly to see if the state of all Shifts in the system have changed. The polling script that goes out and looks for those changes runs on a 5 minute schedule, every 5 minutes. You can schedule Shifts on a per minute basis, so sometimes even a short Alert window of 5 minutes might result in a 9 minute total delay. Here's an example: The polling script runs after a Shift has already started… 4 minutes ago. It doesn't meet the requirement of over 5 minutes to Alert, so nothing goes out. Then, it will wait another five minutes to run again. At this point, the script will catch that there's a Shift that hasn't been Alerted on, but that is over the 5 minute threshold… now at 9 minutes. Please be aware of this behavior.
Alerts in Inbox
Alerts Message Example
To Do:
Save alerts to the database, which will allow for a Time Series Dashboard Widget that can help form a clearer picture of Time & Attendance trends… which will help Markets better handle staff accountability and compliance. Coming soon!
Work Order
This section allows Admins to set alert intervals on expiring Work Orders. This allows Management time to follow up with Clients before contracts end.
The forms are the same but are divided up for Billing and Sales recipients separately.
Expiring Patrol Work Order Sales/Billing
- Alerts
- Alert 4 and 2 weeks before contract expiration
- Alert 3 weeks before contract expiration
- Alert 4 weeks before contract expiration
- Recipients - One or many Manager Users
- Message - Multi-line text box.
- Active - Admins can deactive the feature while preserving settings
Billing
This is where Admins are allowed to set the New Billing parameters that effect the behavior and output of the New Billing Reports.
Period Start Dates: Weekly & Bi-Weekly
- Weekly Start (Weekly periods featured in the New Billing Cycle Filter will start and end according to the date set here)
- Bi-Weekly Start (Bi-Weekly periods featured in the New Billing Cycle Filter will start and end according to the date set here)
Billable Holidays:
Collection of billable holidays that will apply Holiday Rates in New Billing Reports on Tours that start on any of the days featured here, and for any time spent working Shifts that cover (either in part or in whole) any of the days featured here.
Billable Reminders:
This feature is NOT yet available and is under development. We have made this setting available for those that are interested in receiving daily billing notices as soon as it's made available.
- Recipients (a list of Admins in the system that can elect to receive daily billing reminders)
Dash
These settings pertain to the Dash.
Roster Text
Roster Text is where Admins are allowed to set the Header and Summary text of the Call Roster Widget. The text will be featured, respectively, above and below available Users as their Schedules dictate. Call Schedules for Management Users can be added through the Call Roster.
- Header Text - Multi-line text box
- Summary Text - Multi-line text box
- You can deactive the Call Roster Widget while still preserving settings
Access Info Text (Codes in Legacy)
This Widget appears below the Call Roster, and can be used to give generic Location Access info to Internal Users. Those things may include:
- Lock Box Combinations
- Local Management Contact Numbers
- Key Codes
You can deactive the Access Info Widget while still preserving settings.
Note: Careful not to give sensitive information that even some Internal Users might let slip, accidentally or otherwise. This could very easily become a liability if not used correctly and with caution.
Page Footer Text (Page Title in Legacy)
This is standard boilerplate information that you may want to feature on your Dashboard. Caution should be used as to what information is available here as it is available to ALL users Internal or otherwise. Clients CAN and will see this upon reaching the Dashboard.
This exists outside of and below the other left-hand Widgets.
You can deactive the Page Footer Text while still preserving settings.
Client
Report Automation: Category Alerts & Recipients
This section allows Admins to set Alert Recipients and triggers based on Client Report Categories.
Triggers:
- Alert whenever an activity report gets flagged for attention
- Alert whenever an incident report gets logged
- Alert whenever a maintenance report gets logged
Recipients:
- Site Managers (will delegate Alerts to Site Managers based on what Locations have been assigned to their Accounts. Any Shift created for a Location or Group containing at least one of their assigned Locations will be monitoring for Alerts)
- List of Active Manager Users (all Active Users other than Clients, Cops, and Civilians. If any of these are selected, they will be considered recipients for ALL Alerts for ALL Locations)
0 Comments