As an administrator, the steps involved in processing a new verification request could be different depending on two broad factors.
1. The Type of Verification Badge
Segment-based Verification Badges: In this case, a specific criterion is defined. Any record seeking a badge must meet this criterion first. If it doesn't, you'll need to update the record before granting the badge. (Dynamic)
List-based Verification Badges: These badges have no specific criterion. You just need to add the record to the ''approved list'' for that badge. (Static)
2. The Nature of the Applicant's Email
Email Exists in the Database: If the applicant's email already exists in your database, the application will be auto-mapped to this record. You just need to review and approve the application to add this new badge to the record.
New Email: If the applicant uses a new email, you'll need to first add this new email to a record, either by mapping it to an existing record or by creating a new one.
The process to reject the application is the same in both cases. You can review the form entries and hit the reject button if you feel the user is ineligible for the badge. Please note that rejecting an application does not automatically notify the user. We recommend using the "reply by email" button to send the user a message via email and then rejecting it.
The following videos walk through the steps in processing applications for a couple of different scenarios.
Part 1:
List-based verification badges
Applicant's email is already on file
Part 2:
Segment-based verification badges
The applicant's email is not on any record in your database.
To learn more about managing verification badges, click here
To learn about creating verification forms, click here
For any further questions or assistance, please contact us at help@almabase.com or through the Intercom Chat 💬. We are here to assist you! 😄