# End-user experience - Link: https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/end-user-experience/ - Published: 2026-08-24T01:47:07+00:00 - Author: Don Bowman 1. [Home](https://www.agilicus.com/) 2. [Agilicus AnyX Administrative Web Interface](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/) 3. [Concepts](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/) 4. End-user experience ![f4181a45-featured-anyx-admin-conceptsend-user-experience](https://www.agilicus. com/www/f4181a45-featured-anyx-admin-conceptsend-user-experience.png) ## End-user experience [CONTACT](https://www.agilicus.com/contact-us/) The portal is the administrator’s view of Agilicus AnyX. This page explains the other side: what users experience when they connect. Understanding this helps you configure resources correctly and answer support questions. ## Signing in Users sign in at a URL served from your domain (through your CNAME). They see your organisation’s sign-in page, themed to match your brand (see [Sign-in theming](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/authentication/theming/)). They authenticate with their existing identity provider, and complete multi-factor authentication if your [authentication policy](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/authentication/authentication-policy/) requires it. There is nothing to install for browser-based access: a user just opens the URL and signs in. ## Browser access For **web applications** and **file shares**, users work in the browser: * applications open in the browser through the identity-aware proxy (see [Applications](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/applications/)); * shares are exposed over HTTPS and WebDAV, so users can browse files in the browser or mount them in a file manager (see [Shares](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/shares/)); and * templates can be requested or downloaded (see [Templates](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/templates/)). ## The launcher For resources that do not fit in a browser, users install the **Agilicus launcher** on their desktop. The launcher gives access to: * **SSH** services (see [SSH](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/ssh/)); * **databases** (see [Databases](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/databases/)); * **desktops** through a remote desktop client (see [Desktops](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/desktops/)); and * other TCP-based resources. The launcher signs the user in once, and then each resource is one click away. Installation instructions and troubleshooting are in the web guide’s [Launcher (desktop)](https://www.agilicus.com/product-guide/launcher-install-desktop) and [Launchers](https://www.agilicus.com/product-guide/launchers) pages. ## Requesting access If the [request flow](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-requests/) is enabled, a user who does not yet have access can request it from the portal. The request is sent to administrators for approval. Until approved, the user cannot access the resource. ## What users never see With zero trust access: * users never need a VPN; * users never connect to a public IP of your resources; * users never see your internal network topology beyond what you deliberately expose; and * when a user leaves the organisation, their identity is removed and their access stops. ## Troubleshooting from the user’s side If a user reports a problem, the usual questions are: 1. Can they sign in? (Check the [authentication audit](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/organisation/authentication-audit/).) 2. Are they allowed? (Check [permissions](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-permissions/) and [policies](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/access/policies/).) 3. Is the resource reachable? (Check [connector diagnostics](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/connectors/).) 4. What did the request look like? (Use [application diagnose](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/applications/).) ## See also * [Zero trust architecture](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/zero-trust-architecture/) * [Identity and authentication](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/identity-and-authentication/) * [Resources](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/resources/) * [Launchers](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/launchers/) * [Shares](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/shares/) * [Desktops](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/desktops/) ## Web guide * [Launchers](https://www.agilicus.com/product-guide/launchers) * [Launcher (desktop) install](https://www.agilicus.com/product-guide/launcher-install-desktop) * [Zero-trust desktop access](https://www.agilicus.com/product-guide/zero-trust-desktop-access) * [Zero-trust SSH access](https://www.agilicus.com/product-guide/zero-trust-ssh-access) * [Application request access](https://www.agilicus.com/product-guide/application-request-access)