> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-white-papers/captive-portal/external-splash-page.md).

# Integrate with External Splash Page

Using an external splash page allows you full control over the sequencing and presentation of a splash page. Alternatively, [i](https://help.cloudtrax.com/hc/en-us/articles/204803954-Internally-Hosted-Splash-Page-with-RADIUS-Authentication)nternal splash page are simpler, but provide less flexibility. External splash pages are stored and executed on a web server that user define, and must respond appropriately to certain messages from the Access Point in order to present appropriate user-interface to the user at various stages of the authentication process.

When combined with RADIUS Authentication, EnGeniusCloud will consult an external RADIUS server that you specify in order to determine whether to authenticate the user. The user interface presented to the user will be determined by the external splash page.

Most EnGenius customers who need a captive portal authentication system on their wireless networks use the customizable splash pages that are hosted by EnGeniusCloud. However, some network administrators may prefer to host a captive portal page on their own servers. This Section shows you how to configure EnGeniusCloud to adopt external splash page with an external RADIUS server to handle authentication.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/home-cloud-white-papers/captive-portal/external-splash-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
