> 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.md).

# Resources

Plan internal equipment, track availability, and charge resource usage in OutSmart.

**Resources** helps you manage internal equipment in OutSmart.

Use it for trailers, vehicles, cranes, tools, and other shared assets.

{% hint style="info" %}
Resources is available from **Boost** as a Power-Up.

It is included in **Accelerate** and **Maximize**.
{% endhint %}

### In this guide

This section covers:

* [**What is Resources?**](/marketplace-packages-and-power-ups/power-ups/resources/what-is-resources.md)
* [**Activate Resources through the License Manager**](/marketplace-packages-and-power-ups/power-ups/resources/activate-resources-through-the-license-manager.md)
* [**Resources availability and plans**](/marketplace-packages-and-power-ups/power-ups/resources/resources-availability-and-plans.md)
* [**Features in Resources**](/marketplace-packages-and-power-ups/power-ups/resources/features-in-resources.md)
* [**Eligibility and requirements for Resources**](/marketplace-packages-and-power-ups/power-ups/resources/eligibility-and-requirements-for-resources.md)
* [**Test plan for Resources**](/marketplace-packages-and-power-ups/power-ups/resources/test-plan-for-resources.md)

### What you do with Resources

With Resources, you can:

* register internal equipment
* plan equipment in the Scheduler
* link resources to work orders
* charge resource usage with tariffs

### Quick QA checklist

Use this checklist to confirm Resources is set up correctly:

* Resources is available for the current plan.
* The feature is activated in the account.
* Users can open the Resources area in the BackOffice.
* At least one resource category exists.
* A test resource can be created and saved.
* The resource is marked as internal.
* The resource appears in the Scheduler after assigning a category.
* The resource can be linked to a work order.
* Tariff fields work if usage-based charging is enabled.

### Recommended order

1. Start with [**What is Resources?**](/marketplace-packages-and-power-ups/power-ups/resources/what-is-resources.md).
2. Then [**activate Resources**](/marketplace-packages-and-power-ups/power-ups/resources/activate-resources-through-the-license-manager.md) if needed.
3. Check [**plan availability**](/marketplace-packages-and-power-ups/power-ups/resources/resources-availability-and-plans.md).
4. Continue with [**Create and manage resources**](/marketplace-packages-and-power-ups/power-ups/object-management/create-and-manage-resources.md) for the setup and daily work.
5. Use [**Test plan for Resources**](/marketplace-packages-and-power-ups/power-ups/resources/test-plan-for-resources.md) for QA, UAT, or regression checks.

### Related topics

* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.md)
* [**Create and manage resources**](/marketplace-packages-and-power-ups/power-ups/object-management/create-and-manage-resources.md)
* [**Test plan for Resources**](/marketplace-packages-and-power-ups/power-ups/resources/test-plan-for-resources.md)
* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/resources.md?ask=<question>&goal=<user_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.