> For the complete documentation index, see [llms.txt](https://docs.secureaccess.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secureaccess.com/documentation/admin-guide/configure-your-applications.md).

# Configure your applications

## Add a new domain

On the left side menu, click on ***Sites >> Domains***.

Once inside click in:

<div align="left"><img src="/files/-Lc76vfpwwVJR6xVVs83" alt=""></div>

And you will see a form to enter a new domain name.

![Image 1: Domains management page](/files/-Lc784f3qk8xgC96MUEz)

## Add a new subdomain

In the section ***Sites >> Domains*** you can add a new subdomain to a previously registered domain. Press the next button:

<div align="left"><img src="/files/-Lc78Muy7aLEIetqpQa9" alt=""></div>

And once pressed press the next button:

<div align="left"><img src="/files/-Lc78ZxDzagjtFJYYYTa" alt=""></div>

![Image 2: New subdomain form](/files/-Lc78gQRI0IKuA6aL5PK)

The process will consist in 6 simple steps to configure all the necessary information to protect your web application with *SecureAccess® CLOUD*:

* In the first step we will be asked to point the *DNS* of the resource to our secure server ***my.secureaccess.com***<br>
* In the second step you must enter general data about your subdomain, like description, name and communication protocol (*HTTP/HTTPS*).<br>
* In the third step you need to add the IP address of your server. You can add more than one and *SecureAccess® CLOUD* will act as a load balancer. <br>
* Fourth step will allow you to create a list of whitelisted IP address, request coming from this address will skip authentication process for this subdomain. \
  \
  **This will disable the access control mechanism, so use it carefully**.  <br>
* In the fifth step allow you to upload your own *SSL* certificate for the HTTPS communication. In case you don´t have one, *SecureAccess® CLOUD* can generate one for you. To use this option, you must first point your subdomain *DNS* to our reverse proxy (***my.secureaccess.com***). In a few seconds your new certificate will be generated and ready to use.  Select the option that fits you better and click on Next. <br>
* Last step gives you the opportunity of enabling *SecureAccess® WAF* (*Web Application Firewall*), which will analyze all the requests going through the platform blocking the ones containing malicious content. This will help in the prevention of *SQL injection* or *XSS* attacks. As an administrator you will receive notifications and alerts when a request is deemed suspicious and therefore blocked. 

Once all steps are done, you can press:

<div align="left"><img src="/files/-Lc792aU3mI9BXfRiChC" alt=""></div>

And your subdomain will be registered and enabled.


---

# 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://docs.secureaccess.com/documentation/admin-guide/configure-your-applications.md?ask=<question>&goal=<endgoal>
```

`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.
