> 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/understanding-the-app-config-fields/support-emails.md).
# Contact Emails
## Updating Your Application Contact Emails
Keep the contact email addresses for your Production application up to date in the Singpass Developer Portal. Singpass administrators use them for:
* Service announcements and changes
* Migration or compliance deadlines
* Technical or operational notifications
* Requests for action or clarification
### Update your Production contacts
Singpass primarily contacts the persons listed for your Production application. Keep these details accurate and update them when team members, responsibilities, or email addresses change.
Outdated contacts may cause your team to miss important updates or required actions. Where appropriate, use a monitored team or shared mailbox alongside individual addresses.
### How to update your contact emails
1. Sign in: Log in to the Singpass Developer Portal at `developer.singpass.gov.sg`.
2. Select Production: Open the Production environment.
3. Open your application: Select the application you want to update.
4. Edit details: Open the option to edit your Production application details.
5. Update and save: Review the contact email addresses, make changes, and save.
For detailed instructions, refer to the [guide on editing Production apps](https://app.gitbook.com/o/oIOKcTCZC2fptOuInlww/s/OV8xmtJpBBV1NehZlKZb/).
### Your responsibility
Review your Production contacts regularly and whenever your team changes. Keeping them current ensures the right people receive important Singpass communications and can act promptly.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.developer.singpass.gov.sg/docs/singpass-developer-portal-sdp/understanding-the-app-config-fields/support-emails.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 `build a script that syncs our docs to a CMS` 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.
