Now more than ever it’s important to have control over who is allowed to sign in on site. With rejected sign ins, you can block a visitor sign in depending on the response to a custom field. This how-to-guide will walk through the set up for a rejected sign in on a custom field and how to notify the right people in this scenario.
Sign in field
To get started you need to create a new sign in field or edit an existing one. From the online management portal, navigate to Manage > Sites > Select the site > Sign in & out > Sign in fields and either click to edit an existing field or click Add sign in field to create one.
Rejected sign ins can be added to Dropdown, Dropdown with other, and Yes/no question field types. When adding a dropdown or yes/no question, under Reject sign in based on answer, make your selection for which answer will cause a rejected sign in:
Rejected sign in message
When a sign in is rejected it's important to convey why this has happened. You can add a message to the screen from the Rejection message box. This message will be the same across the iPad/android app and contactless sign-in.
Rejected sign in notifications
As well as letting a visitor know they're not able to sign in, it is important to make all relevant team members aware. Through email, SMS, Slack and MS Teams you can notify the right people that a rejected sign in has been recorded.
Host notifications
When a visitor’s sign in is rejected you might want to make their host aware. You need to ensure that host notifications are configured for the group that contains your hosts. Go to Manage > Visitor Groups > Select your host group > Host Notifications and ensure Allow this group to be selected as hosts is selected. You can read more about host notifications here.
The notification will look similar to the below, depending on the notification type selected for the group (Email/SMS/Slack).
Rejected sign in notifications will highlight the field that caused the sign in to be rejected. This helps you to quickly identify why a visitor has had their sign in rejected.
Important: Depending on how the visitor is signing in, their sign in might be rejected before they’ve provided the information on who they’re visiting. For this reason we recommend adding the custom field where the visitor specifies the host before any custom fields set up to reject a sign in.
You can configure this by going to Manage > Groups > Select group > Sign in & out and reordering the fields.
Group notifications
Group notifications allow you notify anyone else who needs to be aware in the case of a rejected sign in. To set this up, head to Manage > Advanced Notifications where you can either click to edit an existing notification, or click New notification to add a new one. The trigger should be set to Rejected sign in:
We hope you've found this guide useful but if you have any questions around Rejected sign ins or any Sign In App feature, please contact our support team at [email protected].