> For the complete documentation index, see [llms.txt](https://docs.developer.singpass.gov.sg/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developer.singpass.gov.sg/docs/singpass-developer-portal-sdp/app-management/create-staging-test-account.md).
# Create Staging Test Account
**Prerequisites:**
* Ensure you are logged in to the [Singpass Developer Portal](https://developer.singpass.gov.sg)
* Switch your Dashboard view to **Staging**.
* You have at least one Staging App.
{% stepper %}
{% step %}
### Click on the App Name
Click the **App Name** link on your Dashboard — Staging view.
{% endstep %}
{% step %}
### Click Test Accounts
You will be redirected to view the Staging App details. On the left menu, click **Test Accounts**.
{% endstep %}
{% step %}
### Click Create
You will see the list of test accounts. Click **Create**.
{% hint style="info" %}
You can create a maximum of **5 test accounts**. Test accounts are not restricted to a specific app.
{% endhint %}
{% endstep %}
{% step %}
### View your new test account
A new test account is created and displayed. Click the eye icon to view the account password.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.developer.singpass.gov.sg/docs/singpass-developer-portal-sdp/app-management/create-staging-test-account.md?ask=&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.
