> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-app-manual/untitled.md). # 9.0 – Well Seeker Admin This section is only available to users with the **Admin** permission enabled on their user account. Gives an organizations administrative users access to their organizations Well Seeker Pro and Innova Engineering usage data. The admin can also deactivate and reactivate Well Seeker Pro and Innova Engineering licenses from this interface. ## 9.1 – Current User Details Displays a list of individual Well Seeker Pro and Innova Engineering devices using your company build of the software. Information displayed includes device, IP address, version, location, and last time active information. When the user selects a listed device the message “**Well Seeker user** **Are you sure you wish to change?**” If **No** is selected, then this action will be cancelled and no change will be made. If **Yes** is selected, then the license status for this device will be changed i.e. from active to deactivated, or from deactivated to active. ## 9.2 – Usage Summary Displays the number of Well Seeker Pro and Innova Engineering users for each day over the past month, along with the minimum, average and maximum daily usage figures. ## 9.3 – Usage Map Displays the location of each Well Seeker Pro user on the map. Select the user marker on the map to see their user details. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.innova-drilling.com/introduction/innova-engineering-manual/innova-app-manual/untitled.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.