Mokka employs robust mechanisms to identify users and manage their authorization, ensuring data security and accurate record-keeping. This is crucial for both internal users and external participants like candidates.

How Mokka Identifies Users

Mokka primarily identifies users through unique identifiers. These can originate from two main sources:

  • External Identifiers: For users integrated from external systems (e.g., an Applicant Tracking System or HR Information System), Mokka utilizes the unique identifier provided by that system. This ensures consistency across platforms.
  • Internal Identifiers: For users who interact directly with Mokka without an existing external identifier (e.g., a candidate who applies directly through a Mokka-hosted form), Mokka generates a unique internal identifier. This guarantees that every user within the system has a distinct and traceable ID.

The 'Invited by Email' Field

The 'invited by email' field plays a critical role in both data retrieval and authorizing self-service actions, particularly for external users.

  • Purpose: This field stores the email address used to invite or communicate with a user. It acts as a key to link specific data and actions to that individual.
  • Data Retrieval: When Mokka needs to retrieve data associated with a user, it can use the 'invited by email' field to accurately locate and display relevant information.
  • Self-Action Authorization Checks: For actions where a user needs to verify their identity to perform an action on their own data (e.g., a candidate updating their profile), Mokka uses the 'invited by email' field to confirm that the user attempting the action is indeed the owner of the data. This prevents unauthorized access or modifications.

Handling Null Values in 'Invited by Email'

If the 'invited by email' field is null (empty) for a particular user record, Mokka cannot use this field for email-based data retrieval or self-action authorization checks. In such scenarios:

  • Data Retrieval: Any data retrieval operations that rely solely on matching the 'invited by email' field will not be able to locate the record using this specific criterion.
  • Self-Action Authorization: Self-service actions that require authorization via the 'invited by email' field will not be possible for that user. The system would need to rely on other available identifiers or authorization mechanisms, or the specific self-action might be restricted if email is the primary authorization key.