ChurchInsight  is now

Support for Hubb users

How can we help you today?

Support > Check-in > Check-in Event settings

Event settings

These are settings that apply to all Check-in groups for a given event – e.g. the kiosk background. You can also set a default profile/open/close time that will apply to all groups assigned to this event (unless specifically overridden). Event specific settings are:
  • Enable Check-in
This must be ticked for this event to appear on
  • Check-in Profile
This is the profile that will be used for groups assigned to this event. If a specific value is set here, it will override any specifically set or inherited value in the check-in group’s settings. A specific value set here could be overridden by a specific value set for the group on the Check-in Groups tab of the event.
  • Automatically include event group in check-in
By default, the group in which the event was created will be used as the check-in group. You can also manually add additional check-in groups to an event. If you don't want the group in which the event was created to be used as one of the check-in groups for the event, untick this box.
  • Leader term
A leader at an event is a group Leader in the database. Here you can specify the term that will be used on their label e.g. Kids Team Leader, to match your standard terminology.
  • Kiosk background
This image is used as the background on your public check-in kiosks
  • Security mode
When registering a family with multiple children, you can choose to have either the same or a different security code printed on each child label. If the same security code is used for the whole family, only one set of guardian labels is printed and any guardian can collect any child. If different security codes are used for each child, specific matching guardian labels are also printed for each child.
  • Leader password
When a leader is assisting an attendee at a kiosk, they can use the password to perform admin functions such as re-printing labels, viewing the register of those checked-in or absent, or sending emergency SMS messages to guardians. A kiosk will always require a proper Hubb log-in to launch it, so this is just a secondary password to limit access to a few functions once the kiosk is launched. You can give it out to your helpers as you see fit.
  • Open time
When launching a kiosk, the list of check-ins shown only includes open ones by default. So set this to the earliest time you want to be able to launch a kiosk before people start arriving at the event.
  • Close time
The time that check-in will close for each check-in group relative to the event end time. When a check-in closes for a group, no one else will be able to check-in or out of that group at a kiosk, temporary users will be deleted, and the check-in close summary email will be sent.

 These settings can either be set on a specific event, or inherited as detailed in the following section.

Setting Inheritance

  • An Event is always in a group, but multiple groups can be assigned to an Event from anywhere in the tree for Check-in.
  • Check-in settings are inherited from 4 levels: Hubb defaults -> Check-in Global Settings (under site settings) -> Check-in Group settings (from the root group down) -> Event Check-in settings.
  • The group tree that is used for inheritance depends on the setting, according to the following diagram


Special cases: Check-in Profile, Open & Close time
Once attendance tracking or a Check-in kiosk has been launched for the first time, these three inherited settings are stored for each check-in group for that event. The stored values are then used by any future Check-in kiosk launched for that event. This is to ensure consistency across all your Check-in kiosks. If you need to, you can delete any of these individual stored values:
  • Open the Event editing screen for the relevant event.
  • Under the Check-in Groups tab, find the row for the check-in group and click the orange reset arrows to remove the stored settings.
  • The next time an attendance session or Check-in kiosk is launched, the values will be looked-up fresh as per the inheritance tree above and will then be stored again.