> 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/quality-managers/implementing-capas-apps.md). # Implementing CAPAs (Apps) Use the CAPA application to create, manage, and track corrective and preventive actions. ## Overview The **CAPA** application is a structured, workflow-driven solution for managing corrective and preventive actions. It supports the full lifecycle of a CAPA, from creation and review to root cause analysis, resolution, and closure. {% hint style="info" %} All reports are logged, assigned, and tracked in a centralized system, ensuring visibility, accountability, and compliance with organizational standards. {% endhint %} *** ## Application Prerequisites Before users can work with the **CAPA** application, administrators must configure the following settings:

General Settings

**Location** Define geographical or operational locations relevant to your organization. **Compliance Program** Define compliance programs applicable to your organization. **Frequency** Define the intervals at which activities are scheduled to occur. **Category** Define categories for classifying and organizing activities across the organization. **RCA Reason & Description** Define root cause analysis reasons and related descriptions.

CAPA Settings

**Related To** Define links between CAPAs and other entities.

Action Item Settings

**Effectiveness Check** **Duration** Define durations used for effectiveness checks.

Product(s) / Equipment Application

**Product /** **Equipment** Define products relevant to your organization.

{% hint style="success" %} For detailed setup instructions, see [**CAPA Application Settings**](/interfacing-help-files/administration-and-configuration/configuring-application-settings/capa-application-settings.md). {% endhint %} *** ## Accessing the Application To access the **CAPA** application: 1. Select the **Apps** tile in the side navigation bar. 2. On the **Apps** page, either: * Expand **CAPA** in the navigation tree, or * Navigate to the **CAPA** section in the application gallery.

IMAGE

The application opens, displaying its available modules.


New CAPA	Use this module to create and submit a new CAPA for review and processing.
CAPA List	Use this module to view all submitted CAPAs, tracking progress through the workflow.
CAPA Reminder	Use this module to send reminders to responsible users for pending tasks.

{% hint style="danger" %} Available modules vary based on your assigned permissions. {% endhint %} *** ## Learn More Refer to the following guides for detailed instructions:

		Role(s):	Related Module(s):			Cover image
How to Create & Manage CAPAs	Perform assigned tasks to advance reports through the CAPA Management workflow.	Reporter, Reviewer, RCA Owner, Action Owner, Eff. Check Responsible	New CAPA			IMS-V16-NAV-Library-Icons-64.png	Creating & Managing Quality Events
How to Track & Monitor CAPAs	Monitor the status and progress of CAPAs using lists and dashboards.	Reporter, Reviewer, RCA Owner, Eff. Check Responsible	CAPA List	CAPA Dashboard	CAPA Reminder	App-V16-Icons-1.png	Tracking & Monitoring Quality Events

--- # 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/quality-managers/implementing-capas-apps.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.