> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/attach2dynamics/how-to-guides/configuring-hierarchy-structure.md).
# Configuring Hierarchy Structure
Attachments/Documents of Dynamics 365 CRM records can be stored in SharePoint sites on the basis of hierarchy. To achieve this, follow the steps given below:
* Go to **Advanced Settings --> Settings --> Document Management Settings.**
* Select **Entities --> Enter the URL of respective SharePoint site.**
* Enable the Checkbox **‘Based on Entity’** **--> Select either of the entities, Account or Contact --> Click on Next.**
* Click on **Finish.**
* When hierarchy is enabled, the path structure will look as shown below.
* Next, go to **Opportunity --> Select an opportunity --> Click on Attach2Dynamics button --> Drag and Drop required file.**
* Next go to SharePoint site. Here, the respective file will be stored in the following manner: **Account > Account Name\_guid > Opportunity > Opportunity Name\_guid.**
{% hint style="success" %}
For any queries, reach out to us at
{% endhint %}
---
# 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.inogic.com/attach2dynamics/how-to-guides/configuring-hierarchy-structure.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.