---
title: Configuration by use case
description: Configuration steps vary depending on what type of deployment you are implementing.
component: pingaccess
version: 9.0
page_id: pingaccess:reference_guides:pa_configuration_by_use_case
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/reference_guides/pa_configuration_by_use_case.html
revdate: February 6, 2023
section_ids:
  next-steps: Next steps
---

# Configuration by use case

Configuration steps vary depending on what type of deployment you are implementing.

For a detailed discussion of deployment considerations and best practices in designing your architecture, see the [Deployment Guide](pa_deployment_guide.html). The following sections describe the configuration steps for the most common use cases:

* [API Access Management Gateway Deployment](pa_api_access_management_gateway_deployment_table.html)

* [Web Access Management Agent Deployment](pa_wam_agent_deployment_table.html)

* [Web Access Management Gateway Deployment](pa_wam_gateway_deployment_table.html)

* [Auditing and Proxying Gateway Deployment](pa_auditing_and_proxying_gateway_deployment_table.html)

## Next steps

After you complete the above configuration settings, the following steps are similar for all use cases:

* Configure sites and agents to define the target applications you want protected. Sites might need site authenticators to define the credentials the site expects for access control.

* Configure applications and resources to define the assets you want to allow clients to access.

* Create policies for the defined applications and resources to protect them.