Recommended Involvements ================= The Recommended Involvements feature was built especially for those who already exist in your database, but are not yet assigned to a class. Recommended Involvements is an unmanned process for handling load balancing and overflow scenarios. Also, the long-lost sheep or spotty attender who has been dropped from rolls will have an option for check-in without needing an attendance to use "Visit" or "Join." Check the box to enable. Previously, Admin Mode was needed to first add someone to an involvement and then check them in. Using Recommended Involvements speeds up that process. Key Points to Consider ---------------------- * This is designed specifically for people who *already exist* in your database. If the family is brand new, they will need to visit a kiosk with Admin Mode or a manned kiosk. * All steps below must be followed for this feature to work correctly. Setting Up Recommended Involvements ------------------- Step 1 - Configure the Involvements Identify and set your recommended involvements. These can be exisiting or new. Go to the `Settings > General` tab in the Basic Setup section. Set `Join Type for Recommended` to either **Guest** or **Member**. .. seealso:: :doc:`/Organizations/GeneralSettings` Step 2 - Set up Check-in Profiles The following profile settings pertain specifically to Recommended Involvements. .. figure:: https://i.tpsdb.com/Staci/RecommendedGeneral.jpg :target: # **Enable Recommended** - If checked, this will enable Recommended Involvements. **Meeting Start Time** - This is the time at which you want Recommended Involvements to be available. It does not need to correspond with a specific meeting time. **Meeting End Time** - This is the time at which you no longer want Recommended Involvements to be available. It does not need to correspond with a specific meeting time. **Recommended Based On** - This allows you to control whether involvements are recommended based on Capacity or Least Attended. If it is set to Capacity, all involvements in the grouping must have a capacity set on the schedule or meeting. When set to **Capacity**, the first recommended involvement in the grouping will be shown until the capacity is reached. At that time, the next class listed will show. When set to **Least Attended**, the recommended involvement with the least amount of people already checked in will be shown. .. note:: If a class is closed for any reason (capacity reached or manually closed), that involvement will not show up. You can easily see whether or not a class is closed by going to the Check-in Dashboard. .. seealso:: | :doc:`CheckInProfiles` | :doc:`CheckInDashboard` Step 3 - Manage Recommended On the same page where check-in profiles are added, there is a button in the upper right hand corner that says **Manage Recommended**. This is where you go to add your groupings. There is no limit to the amount of groupings that can be added. .. figure:: https://i.tpsdb.com/Staci/managerecommended.jpg :target: # **Enable** - You can easily toggle between Enabled and Disabled. **Campus** - Campus selector. **Recommended By** - You can choose to recommend involvements by Grade, DOB or Position in Family. .. note:: If you choose **Grade**, you need to have a Start grade and End grade. If you are only including one grade, set Start and End as the same grade. **Show Label** - If this box is unchecked, the class will show, but it won't have a "Recommended" label in check-in. If checked, the "Recommended" label will appear. **Involvements** - This is where you add the recommended involvements. Step 4 - Configure Check-in Administrative Settings There are a couple of optional settings to pay attention to that will affect Recommended Involvements. These settings can be found under `Admin > Advanced > Settings > Features > Check-In` **Early Checkin** - The number of minutes before a meeting starts when people can start checking in. You can override this in the involvement's check-in settings. **Late Checkin** - The number of minutes after a meeting starts when people can start checking in. You can override this in the involvement's check-in settings. **Exclude from Recommended** - If a person is in this Status Flag, they should NOT see Recommended Involvements during check-in. .. seealso:: :doc:`/People/StatusFlags` Step 5 - Testing Now it is time to test this to make sure it all looks as expected. .. figure:: https://i.tpsdb.com/Staci/recommendedchecking.jpg :target: # .. seealso:: | :doc:`CheckInOperation` | :doc:`PreCheckIn` | | +--------------------+------------------+ | **Latest Update** | **02/28/2024** | +--------------------+------------------+ Updated menu location