> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/getting-started-and-navigation/page_inspection.md).
# Page Inspection
Inspect a page to see its page ID, table, fields, and extension context for troubleshooting.
All pages in Bevica SaaS have a Page Inspection section. Page inspection shows you information that might be useful in admin & support situations. It shows information about the page, its different elements, and the source behind the data it holds. For example, you can see fields like **Created By** and **Last Modified By** on any record.
{% hint style="warning" %}
**Prerequisites**
Access and permission to read the appropriate record.
{% endhint %}
### Page Inspection
To open Page Inspection click **Ctrl + Alt + F1** from the appropriate page.
#### Useful features:
* **Page / Table fields**. These denote the technical object the page is based on. Could be useful when explaining to the support desk exactly what page you are on.
* **View Table.** This will open a new page showing all records and fields on the table. For larger tables this will take a long time to open so may not be the most efficient way of looking at raw data. For this we would advise to try a Configuration Package.
* **Table Fields.** This lists all field on the table. Some tables have over 100 fields, so rather than scrolling (they are not in alphabetical order), try the **Search** function (Magnifying Glass).
* **Page filters**. Shows if any filters are applied to the page, these might be system filters or ones applied by you.
* **Extensions.** This shows you all the extensions applied to the page.
#### Record Audit
All tables have the following information, search for them on **Table Fields**.
* Created By
* Created Date/Time
* Last Modified Date
* Last Modified Date/Time
---
# 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://kb.bevica.com/documentation/guides/getting-started-and-navigation/page_inspection.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.
