> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/dashboard/database/collections/indexes.md).

# Indexes

To optimize your find queries you can add indexes for your collection. Because we are using MongoDB internally as a provider, indexes should be set according to MongoDB standards.

## Creating indexes

Indexes can be added inside a collection page, **Indexes** tab. Here you need to provide fields with an index value. Optionally you can provide options for an index.

![Index add view](/files/-M-5NOAnKl5XOuw0ZPUS)

To create an index, modify provided **\<field>** and **\<type>** fields. The **\<field>** is your field name (unique name) and **\<type>** is an index value for that field. You can also specify some options. Though options currently are not fully supported so you can leave the options field as it is.

{% hint style="warning" %}
Indexes take up some available storage in your database. So don't overuse indexes if you are nearing your storage limit.

Also, indexes decrease performance when inserting, updating, deleting your records as the keys in the index needs to be adjusted.&#x20;
{% endhint %}

## Index Types

The following provides some available examples displaying various available options for your indexes.

### **Single field index**

Consists of one field. Here **\<field>** is first\_name and **\<type>** is **1**.

```javascript
{ "first_name": 1 }
```

### **Compound index**

Consists of multiple fields. Here we create an index on two fields. In this case **\<field>** representations are **first\_name** and **age**, and **\<type>** representations are **1** and **-1**.

```javascript
{ "first_name": 1, "age": -1 }
```

Here values **1** and **-1** tells how to sort index keys. For a single field the order does not matter. For compound, it matters when using sorting. It matters in two ways:

1. In a sort query, your fields must be **listed in the same order** as in index (although you are not required to use all fields that are in the index, you can use a subset). For example, if you call a find method and provide a sort query`{ first_name: 1, age: -1 }`then index will be used. But if you change positions like this`{ age: -1, first_name: 1 }`then your index will not be used.
2. In sort query your fields must **match the sort direction** as in index or must **match the inverse sort direction** . for example, if you call a find method and provide a sort query `{ first_name: 1, age: -1 }` or `{ first_name: -1, age: 1 }` then the index will be used. But if you only inverse one of the fields like`{ first_name: -1, age: -1 }`then the index will not be used.&#x20;

If you want to put indexes on nested forms, then you can do that separating nested field name and a field inside the nested field by a dot.

```javascript
{ "address.zip": 1 }
```

## External references

As CodeMash is heavily using MongoDB database internally, the following resources explain more on how to form indexes.

* [Full indexes manual](https://docs.mongodb.com/manual/indexes/)


---

# 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://docs.codemash.io/dashboard/database/collections/indexes.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.