> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/3.-non-flaik-related-rtp-configuration/rtp-security-recommendations/security-aspenware-inventory-pools-and-other-config-concerns.md).

# Security - Aspenware, Inventory Pools, & Other Config Concerns

For resorts running Aspenware, there are security level factors to consider

Determining the correct RTP access for the Aspenware (AW) account in RTP is essential - it needs enough access to perform necessary actions, but excess access can have unintended downsides.

The security group associated with the AW account needs to meet the following requirements:

* Is equal or higher than: the product header security for all products sold on AW
* Is equal or higher than: the AW Clearing payment type
* Is less than: the inventory pool override security level for all inventoried products sold on AW

The security issue regarding the inventory pool override level is one that can be overlooked by resorts, but if the AW user can override inventory pools it can push through bookings on days that are already full or aren't even scheduled.

### Recommendation:

* Create an AW-specific security group; set the security access accordingly using the guidelines above
* Set the inventory pool override level above all users access level


---

# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/3.-non-flaik-related-rtp-configuration/rtp-security-recommendations/security-aspenware-inventory-pools-and-other-config-concerns.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.