> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/access/admin-ui.md). # Admin UI The web-based interface for managing, monitoring, and interacting with Connectware. The Admin User Interface (**Admin UI**) is the central web-based management console for interacting with your Connectware deployment. It provides a unified platform for configuring, monitoring, and managing all aspects of the system. While administrators can use the Admin UI to [manage users](/2-6-1/access/user-management.md), configure services, and [register clients](/2-6-1/access/client-registry.md), other users also benefit from role-specific capabilities. For example, depending on assigned roles and permissions: * Engineers can [deploy or update](/2-6-1/data-flows/services/managing.md) service commissioning files to define data flows and resource configurations. * Operators can monitor live production data using tools like the [Data Explorer](/2-6-1/monitoring/data-explorer.md) and view [system status](/2-6-1/monitoring/system-status.md) metrics. * IT and security personnel can review [logs](/2-6-1/data-flows/services/service-logs.md). Role-based access control ensures that each user only sees the features and settings relevant to their responsibilities, maintaining both usability and security. Additionally, all Admin UI functions are also accessible via [REST APIs](/2-6-1/reference/api-reference.md), allowing seamless integration into enterprise systems and automation pipelines. ## Logging Into the Admin UI 1. Open your browser and enter the IP address of your host (**https\://\**).
2. Enter your **Username** and **Password**. When setting up Connectware initially, you can use the [default admin user](/2-6-1/access/user-management/users/default-admin-user.md) to log in. 3. Click **Sign in**. Now you can explore Connectware.
## Finding Your Way Around The navigation panel groups the Admin UI into the following areas. Which areas you see depends on your [permissions](/2-6-1/access/user-management/permissions.md). | Area | What you find there | | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Data** | The [Data Explorer](/2-6-1/monitoring/data-explorer.md) for browsing the MQTT topic tree and monitoring [live data](/2-6-1/monitoring/live-data.md). | | **Services** | The [service views](/2-6-1/data-flows/services.md) for installing and managing services, inspecting [resources](/2-6-1/data-flows/services/service-resources-view.md) such as connections, endpoints, and mappings, reviewing [deviations](/2-6-1/data-flows/services/deviations.md) and [service logs](/2-6-1/data-flows/services/service-logs.md), and testing rules in the [Rule Sandbox](/2-6-1/data-flows/rule-engine/rule-sandbox.md). | | **User** | [User Management](/2-6-1/access/user-management.md) for users, roles, and permissions, the [Client Registry](/2-6-1/access/client-registry.md), and the [Certificates view](/2-6-1/access/security/tls-certificates/ca-certificates/certificates-view.md). | | **System** | The [System Status](/2-6-1/monitoring/system-status.md) views: container status, Internet connectivity, metrics, [agents](/2-6-1/data-flows/agents/agents-view.md), license, and system information. | ## Next Steps * Change the password of the [default admin user](/2-6-1/access/user-management/users/default-admin-user.md) before doing anything else in a production environment. * Create [users and roles](/2-6-1/access/user-management/users.md) so that every person works with their own account and permissions. * Strengthen login security with [Multi-Factor Authentication](/2-6-1/access/user-management/multi-factor-authentication.md) or [Single Sign-On (SSO)](/2-6-1/access/user-management/single-sign-on-sso.md). * Install a sample service and watch live machine data arrive in [Connect Your First Machine](/2-6-1/discover/connect-your-first-machine.md). * Automate anything you can do in the Admin UI through the [REST APIs](/2-6-1/reference/api-reference.md). --- # 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.cybus.io/2-6-1/access/admin-ui.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.