> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/things-manager.md). # Things Manager Manage your IoT devices and the connectivity of your IoT solutions in the Things Manager **The Things Manager includes the following menu items**

		Cover image
Projects	Select the project you want to work to show only the information relevant to that project	icon_projects.png	Projects
IoT Devices	Add and configure new devices, monitor device status, manage device settings, process and interpret data from devices	icon_devices.png	IoT Devices
Connectivity	Manage and control your connectivity for your IoT solutions across all connectivity options	icon_connectivity.png	Connectivity
Processing	Select the data processing options for your data flow and organize your decoders and encoders	icon_processing.png	Processing
Destinations	Connect your IoT data to the location where you want to use it using our destinations options	icon_destinations.png	https://docs.kpnthings.com/kpn-things/building-blocks/destinations
Activity	Track the status and progress of your activities and verify that everything has been processed correctly	icon_bulk reports.png	Bulk actions

--- # 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.kpnthings.com/kpn-things/the-portal-explained/things-manager.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.