> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/sel-faq/using-the-software/cloud-application/historical-activation-and-usag.md). # Historical Activation and Usage Records Whether ENERCALC retains historical activation and usage data to help you decide how many license seats to maintain. I would like to know how many seats I should maintain to be optimally efficient. Does ENERCALC retain historical ***activation*** data that would help me to determine how many seats I should maintain? The menu item License > View Activation and License Information provides info like the Registration Number, License Holder Name, License Type, and Subscription Expiration Date. The menu item License > View List of Activated Computers shows an instantaneous view of the computers that are activated for that license. The activation information that we have access to is only instantaneous. Historical activation data is recorded, but at this time, we are not utilizing it. Soon, we will be using this data to help you determine what your ideal seat count should be. This will not be a sales pitch, but it will provide data to help you make license decisions. I would like to evaluate my company’s usage of ENERCALC to determine how much it is used and what modules are used the most. Does ENERCALC retain historical ***usage*** data? For projects stored locally, we do not collect any usage metrics. For projects stored in our hosted cloud storage, we do not collect any ***detailed usage*** metrics. All we have is "read the calculation records in all the projects in the cloud and tell me what modules were used (and how many times for each module)". This data is currently aggregated across all users, so we cannot tell you which modules you use without running this analysis solely on your files. We can also make the same kind of query for the various governing code options, and the aggregation comments above apply to this as well. If this info would be useful to you, please contact with your request for cloud project usage data. --- # 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.enercalc.com/sel-faq/using-the-software/cloud-application/historical-activation-and-usag.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.