Skip to content

Verification Configuration

Overview

This user story covers the functionality for configuring which credentials require verification, allowing staffing company administrators to streamline verification processes by setting default requirements and overriding them for specific cases.

User Stories

US-CV-02: Configure Credential Verification Requirements

As a staffing company administrator,
I want to configure which credentials require verification,
So that we can streamline our verification processes and focus on the most relevant credentials for our business needs.

Acceptance Criteria

Scenario 1: Setting Default Verification Requirements 

Given I am logged in as a staffing company administrator
When I navigate to the verification configuration settings
Then I should be able to select which credential types require verification by default
And I should be able to save these settings as the organization's default policy

Scenario 2: Configuring Verification Levels 

Given I am in the verification configuration settings
When I select a credential type that requires verification
Then I should be able to specify the verification level required
And I should be able to choose which of the five verification areas are mandatory

Scenario 3: Overriding Defaults for Specific Requests 

Given I am creating or editing a disclosure request
When I configure the verification requirements for this specific request
Then I should be able to override the default verification settings
And the system should apply these specific settings only to this request

Scenario 4: Saving Configuration Templates 

Given I have configured verification settings
When I click "Save as Template"
Then I should be able to name and save the configuration
And I should be able to apply this template to future disclosure requests
And I should see a list of all saved templates

Scenario 5: Editing Existing Templates 

Given I have saved verification configuration templates
When I select a template to edit
Then I should be able to modify the verification settings
And I should be able to save the changes
And the system should ask if I want to apply changes to existing requests using this template

Scenario 6: Audit Logging for Configuration Changes 

Given I make changes to verification configuration settings
When I save the changes
Then the system should log the changes for audit purposes
And the log should include who made the changes and when
And the log should include the before and after state of the configuration

Scenario 7: Applying Configuration Changes 

Given I have updated the default verification configuration
When I save the changes
Then the system should ask if I want to apply the new settings to existing pending requests
And I should be able to choose whether to apply changes retroactively or only to new requests

Dependencies

  • User Management & Authentication
  • Role-based Access Control
  • Verification Process Integration

Notes

  • Only administrators should have access to modify verification configuration settings
  • The system should provide guidance on recommended verification settings for different use cases
  • Configuration changes should be tracked for compliance and audit purposes
  • The interface should clearly indicate which settings are organization-wide defaults versus request-specific overrides