Program Settings

Modified on Thu, 1 Feb at 7:24 AM

Configure the urgency/escalation levels for different audit types from within Program Settings.


Navigate to Settings > Program Settings.

This menu lists each program unique to the site. 


Select an individual program to customize or alter the urgency levels specific to that program. 


When a finding is created, the auditor can select the finding's urgency/escalation level based on the severity of the non-conformance.  



The system automatically inputs a Default urgency level with a 5 day resolution period. 


To create unique urgency level(s), alter the Default level, or use the + Add Level option. 


Next, create the name and description of the urgency level, and also determine the level's resolution period and if this level needs additional approval before a finding can be closed. 



  • Name 
    • The title of this specific urgency level. The title should denote the level of urgency (Low, Medium, High, etc.).
  • Description 
    • Describe the meaning/reasoning for this urgency level.
    • Adding a description is optional.
  • Notification and Resolution Period
    • The level's resolution period determines the due date of the finding. 
    • For example, if a finding is created on March 5th and the urgency level's resolution period is 10 days, the finding is due on March 15th. 
  • Additional Approval
    • If the toggle is enabled, a finding with this urgency level must receive approval prior to being closed.
  • Escalations
    • If the toggle is enabled, users in the corresponding Team(s) will be notified when an audit question fails based on their Urgency Level. When this option has been toggled on, Team(s) must be added. More information on Teams can be found here


Multiple levels can be created for a specific program. 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article