# Sets

### Understanding Sets

Lots of people compare Sets with databases, but there's a key difference: Sets don't *store* objects like regular databases.&#x20;

Sets are a way to see a portion of your graph, and objects you've created, based on your filtered criteria, and several secondary filters which you can customize. You can think of them as a live filter or query for Objects which share certain criteria - specifically, a type or a relation.

#### Sets serve two primary functions:

1. **Organizing and Accessing Objects**\
   \
   We often get requests along the lines of: *How do I find all of the Notes I've created?* \
   \
   One easy way is to create a Set based on Type. \
   For example; Note, which will display every Note you've created in Anytype. \
   \
   If you have specific notes you'd like to frequently access, you can filter them based on Relations you've added to these notes. \
   \
   For instance: Creation Date, Tags, or Priority. (In this sense, Relations behave like attributes).\
   \
   You can then pin your Set to your Favorites menu, where it will sit on your sidebar, acting like a folder for all Objects that meet certain criteria.<br>
2. **Batch editing Objects**\
   \
   Sets also provide a way to batch-edit Objects. \
   \
   You can use multi-select in Sets to delete multiple Objects at once. You can also batch-add or edit Relations for Objects from Set view, instead of entering them one-by-one.

{% embed url="<https://vimeo.com/717016770>" %}


---

# Agent Instructions: 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:

```
GET https://doc.anytype.io/anytype-docs/~/changes/WwUKjnRVmW8csn0Edgm9/anytype-basics/sets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
