> For the complete documentation index, see [llms.txt](https://emca.emudhra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emca.emudhra.com/previous-release-versions/v4.2.6/user-manual/auditor/ca-hierarchy.md).
# CA Hierarchy
The first UI for Auditor is CA Hierarchy. CA Hierarchy is used to display the hierarchical view of CA Certificates (Root and Sub CA certificates). CA Hierarchy defines the certificate chain for each sub-hierarchy in a tree structure where the left-most level is the Root level.
By clicking on a particular CA certificate, the Auditor can
* View certificate details
* Export certificates
For larger sets of CAs, there is also a Search field located above the CA hierarchy. The Search field filters for matching CA names depending on the user input.
By clicking Export on the right side of the detail view, the user can export the CA certificate as
* DER-encoded X.509 certificate (.cer)
* Base64-encoded X.509 certificate (.cer)
* Cryptographic Message Syntax Standard PKCS#7 certificate (.p7b)
The following pop-up dialog will be displayed to select the export format:
Select the export format of your choice and click Download to start the download of the CA certificate. The CA certificate will be downloaded to the standard download location of your OS.
---
# 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://emca.emudhra.com/previous-release-versions/v4.2.6/user-manual/auditor/ca-hierarchy.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.