> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/configuring-application-settings/incident-application-settings.md). # Incident Application Settings Configure and manage settings for the Incident application. ## Overview Before the **Incident** application can be used, administrators (or authorized users) must configure the application settings. *** ## Configuring Application Settings {% stepper %} {% step %} ### Configuring Platform Settings > **Navigation Path (Menu Bar):** `Facilities > Settings` Use this module to establish a connection between the system and the target environment. * **Base URL**: Enter the base address of the EPC server where data is stored. * **Administrator Credentials**: Enter the EPC administrator’s username and password. * Click **Test** to verify the connection. * Once validated, select the environment for data retrieval from the **Default Environment** dropdown. * Click **Save** to apply the configuration. *** {% endstep %} {% step %} ### Configuring QMS Admin Settings > **Navigation Path (Menu Bar):** `QMS > QMS Admin Settings` Use these modules to define options that populate dropdowns across the application. #### General Settings

		Dropdown(s)	Form(s)	Learn More
Location	Define geographical or operational locations relevant to your organization.	`Site`	New Incident Add Action Item	Location
Compliance Programs	Define compliance programs applicable to your organization.	`Compliance Program`	Add Action Item	Compliance Program
Frequency	Define the intervals at which activities are scheduled to occur.	`Frequency`	Add Action Item	Frequency
Category	Define categories for classifying and organizing activities across the organization.	`Category`	New Incident Add Action Item	Category
Currency	Define currencies used when entering cost values.	`Currency Name`	New Incident	Currency
RCA Reason & Description	Define root cause analysis reasons and related descriptions.	`RCA Reason` `RCA Description`	Execute RCA Investigation and Create Actions	RCA Reason & Description

#### Incident Settings

					Dropdown(s)	Form(s)	Learn More
Related To				Define links between incidents and other entities.	`Related To`	New Incident	Create New Incident

#### Action Item Settings

					Dropdown(s)	Form(s)	Learn More
Duration				Define durations used for effectiveness checks.	`Effectiveness Check Duration`	Execute the Action	Duration

*** {% endstep %} {% step %} ### Managing Products / Equipment > **Navigation Path:** `Apps > QMS > Product(s)/Equipment` Use this application to define products that are involved in or affected by incidents.

					Dropdown(s)	Form(s)	Learn More
Product				Define organizational products and equipment.	`Product`	New Incident	Managing Product(s) / Equipment (Apps)

*** {% endstep %} {% step %} ### Managing Suppliers > **Navigation Path:** `Apps > QMS > Supplier` Use this application to define suppliers that are involved in or affected by incidents.

					Dropdown(s)	Form(s)	Learn More
Supplier				Define suppliers associated with your organization.	`Supplier`	New Incident	Managing Suppliers (Apps)

*** {% endstep %} {% step %} ### Managing Organizational Data > **Navigation Path:** `Library > Organization` Use this module to define organizational entities involved in the application workflow.

					Dropdown(s)	Form(s)	Learn More
Departments				Define departments involved in or affected by incidents.	`Business Division` `Business Line`	New Incident Add Action Item	Creating & Editing Organization Objects
Users, Roles, & Groups				Define users, roles, or groups participating in the workflow (e.g., reviewers, action owners).	`Reviewer` `Investigator` `Action Owner` & `Action Reviewer`	New Incident Add Action Item	Managing the Organization

*** {% endstep %} {% endstepper %} *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://interfacing.gitbook.io/interfacing-help-files/administration-and-configuration/configuring-application-settings/incident-application-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.