> For the complete documentation index, see [llms.txt](https://guide.givewise.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.givewise.ca/policy-and-user-documents/demo-access.md).
# Demo Access
## Westwyn Ridge Demo
Welcome to the Westwyn Ridge Wealth demo environment. This sandbox demonstrates how donors and advisors can experience a branded charitable giving platform powered by FlightPath.
#### **Demo Website**
[Westwyn Ridge Wealth – Charitable Giving Fund](https://westwynridge-demo.givewise.ca/)
#### **Portal Login**
***
#### **Donor Account**
**Name:** Hannah Gives
**Email:**
**Password:** Demo2026!
***
#### **Advisor Account**
**Name:** Allan Westwyn
**Title:** Financial Advisor
**Email:**
**Password:** Westwyn2026!
***
#### **Notes**
* This environment is connected to the GiveWise sandbox.
* Data may be reset periodically.
* Please do not change account information or passwords.
* If you experience any issues accessing the demo, please contact your GiveWise representative.
**Last Updated:** July 13, 2026
***
#### **Try These Features**
**Suggested Demo Flow:**
1. Explore the public website.
2. Log in as Hannah Gives.
3. View the Giving Fund dashboard.
4. Make a test contribution.
5. Recommend a grant.
6. Log in as Allan Westwyn.
7. View the advisor dashboard and client management.
---
# 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://guide.givewise.ca/policy-and-user-documents/demo-access.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.