> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/resources/eligibility-and-requirements-for-resources.md).

# Eligibility and requirements for Resources

Before you start with Resources, check the package and account setup.

### What you need

You need:

* an eligible OutSmart package or active Resources Power-Up
* access to the BackOffice
* user rights to manage assets or settings

### What to verify

Check these points first:

* your package is **Boost** or higher
* the feature is active for your account
* the right users can open the resource setup

{% hint style="info" %}
If the resource setup is missing, first check the package, the Power-Up status, and your permissions.
{% endhint %}

### Frequently asked questions

<details>

<summary>Can I use Resources on Launch?</summary>

No.

You need **Boost** or higher.

</details>

<details>

<summary>What if the menu is missing?</summary>

First check the license status and your user permissions.

</details>

<details>

<summary>Do I need the mobile app to use Resources?</summary>

No.

The core setup and planning happens in the BackOffice.

</details>

### Related topics

* [**Resources**](/marketplace-packages-and-power-ups/power-ups/resources.md)
* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Create and manage resources**](/marketplace-packages-and-power-ups/power-ups/object-management/create-and-manage-resources.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/resources/eligibility-and-requirements-for-resources.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.