> **Source:** https://knowledge.leegality.com/document-execution/settings/Department/invitee-configurations > **Site:** Leegality Knowledge Base — https://knowledge.leegality.com > **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration. > **Navigation:** Every article on this site has a plain-text version at `.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt > **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt --- # Invitee Configurations Invitee configurations allow admins to determine which invitee-level options are accessible to senders during the document sending process. Once activated, these options become available for senders to use as needed during the document sending journey. 1. Click on the **Setting ⚙️** icon on the top right corner. 2. Go to **Department > Invitee Configs**. 3. Enable or disable the option as required: - **Reviewer Role:** When enabled, the sender will be able to use Make Reviewer. - **Disable OTP authentication for Reviewer:** Select this and the sender will have the option to enable and disable OTP authentication for the reviewer. - **Group Invitees:** When enabled sender will have the option to create group invitees during the sending journey. - **CC Notifications:** When enabled sender will have the option to add CC invite(s) to the document during the sending journey. - **GPS location and accuracy based restrictions in the signing journey:** When enabled, senders can enable geo-fencing for invitees. You can also specify the default permissible radius and allowed accuracy deviation (in meters). - **Rejection in Signing Journey:** When enabled sender will be able to allow invitees to decline to sign a document. The sender can also require invitees to provide a reason why they are declining to sign. - **Contact Book:** When enabled, the sender will be able to use contacts saved in the contact book. - **Local Language Support:** When enabled, the sender can enable local languages for the invitees. - **WhatsApp Pings:** When enabled, the sender will have the option to send eSign notifications via WhatsApp. - **Face Match Verification:** When enabled, senders can enable face match verification for invitees. - **Acceptance percentage:** The minimum threshold required for successful face match verification. - **Failure treatment:** Configure how to handle verification failures. Select **Reject if Failed** to block the signing process, or **Accept but respond with results** to allow signing while recording the verification result. - **Smart User Liveliness:** When enabled, senders can enable smart user liveliness verification for invitees. - **Acceptance percentage:** The minimum threshold required for successful smart user liveliness verification. - **Mask PII data for Invitees:** When enabled the sender will have the option to enable PII masking for invitees during sending journeys.