> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/reports/creating-reports/creating-a-basic-report.md).
# Creating a Basic Report
This lesson will show you how to create a report to display custom field IDs, which will be useful when creating future reports.
{% stepper %}
{% step %}
### Access the reports page
Reports allow you to sort through your system and extrapolate particular values or groups of values.
This lesson will walk you through the creation of a simple report that will list the IDs of all of your custom fields.
To begin creating your first report, navigate to the reports page by clicking the button on the settings menu under "My Company".
{% endstep %}
{% step %}
### Add a new report
The reports page will list all of the reports you have created on the system. You can also add a new report here by clicking "Add Report". Do this to proceed with creating a basic custom field report.
{% endstep %}
{% step %}
### Name and describe your report
First you must name your report and add a brief description.
{% endstep %}
{% step %}
### Select the entities you want to have listed as columns
The next step is to use the "Entities" list on the left-hand side of the screen to choose the elements you want to add as columns on the table that forms the report.
These are the elements that any conditions applied to the report will sort through. In this case, you will need the fields "ID" and "Name" under "CustomField" in the "Admin Tables" section.
Check the relevant boxes, then click the "Add Column" button highlighted in the screenshot. Your use of labels throughout the system will create categories in the entities list.
{% endstep %}
{% step %}
### Edit your columns
Once you have selected entities to act as columns, they will appear under the "Columns" header in the middle of the page.
Here you can change their title from the entity expression to something more concise and change their order by dragging and dropping them.
{% endstep %}
{% step %}
### Sort your columns
You can also sort the report by a column by clicking the "Sort" button highlighted, then choosing either ascending or descending order.
It is possible to sort a table by multiple columns, which is useful when a report has a high volume of entries.
{% endstep %}
{% step %}
### Set permissions and label the report
You can now set permissions by selecting which user types and groups can access the report and apply system labels using the dropdown menu. When you are finished, save the report to finalize it. You can also preview your results before saving by clicking the "Save Report" button.
{% endstep %}
{% endstepper %}
### Results
This screenshot is a preview of the report created in this lesson. It lists the ID of every custom field created in the system.
---
# 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.agilecase.com/administrator-documentation/reports/creating-reports/creating-a-basic-report.md?ask=&goal=
```
`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.