> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/litigation-use-cases/familiarising-yourself-with-your-documents.md). # Familiarising Yourself with Your Documents When a matter has just been brought before you, it can be quite a challenge navigating through all of the documents shared by your client, especially when the documents themselves cannot be easily distinguished. In this page, we will be showing you the ways in which you can simplify your tasks at the preliminary stage of any proceedings. ## Auto-Folderisation Most of the time, clients share their documents without properly naming their files or creating folders. This leaves the onus upon you to identify which documents should be kept together, resulting in time wasted. Jurisphere's [Auto-folderize](/auto-folderize.md) option allows you to receive intelligent, dynamically generated folders distinguishing the categories each folder falls under, all in a matter of seconds. Simply select the files you wish to folderise, click the auto-folderise button, select litigation and choose the destination folder and you're all set! {% hint style="info" %} **You can auto-folderise your files in anywhere on the platform** That means you could be using [File Library](/file-library/overview-of-the-file-library.md), [Document Review](/document-review/overview-of-the-document-review-tool.md), [Research](/research/overview-of-the-research-tool.md), [List of Dates](/list-of-dates/overview-of-the-list-of-dates-tool.md), etc. and expect the ability to auto-folderise your files to be there across the board! Simply click on 'Browse Files' any time you wish to see your set of documents at any given point of time. {% endhint %} This video will show you how to use the auto-folderise option inside of Jurisphere: **LOOM VID TO BE INSERTED HERE** ## Using File Library to Understand Your Documents So you've created your folders and you can now distinguish the general categories of all the documents you've received. Now it's time to read these documents and actually find out what their contents are. This is where our [File Library](/file-library/overview-of-the-file-library.md) tool comes in, as you can get rapid summaries of each document, using our in-line citations to see exactly where the information has been extracted from. Additionally, you can even see the category of the document, the true title of the document as extracted from within, even the date the document was created on so long as it is mentioned within the contents! {% hint style="info" %} **Documents aren't in English? No problem!** Once your documents are uploaded and our proprietary OCR has been applied to them, Jurisphere is able to read the documents and provide you with their summaries in English, without needing to first translate the document. In fact, this capability applies across the board with our tools, so if you wish to query specific documents that are in a regional language, you can use whichever tool you require and expect our output to provide you with accurate in-line citations (and you can verify it so long as you can read the language of the document). {% 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://help.jurisphere.ai/resources/litigation-use-cases/familiarising-yourself-with-your-documents.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.