Resources
A resource is anything you expose through Agilicus AnyX. The platform treats each resource as an individual, protected object with its own name, address, policy, and permissions. This is what enables precise authorisation: you grant access to a specific resource (or a specific role within it), not to a whole network.
Resource types
| Resource type | What it is | Portal page |
|---|---|---|
| Application | A web application exposed through the identity-aware proxy. Users access it in a browser. | Applications |
| Connector | The outbound-only link between your site and the cloud. | Connectors |
| Database | A database exposed to applications running on the platform (usually through a launcher or an application). | Databases |
| Desktop | A remote desktop, exposed as a remote desktop gateway. Users connect with a remote desktop client. | Desktops |
| Launcher | A small desktop application that gives the user access to resources outside the browser (SSH, databases, shares, and more). | Launchers |
| Network | A global network resource (usually a TCP service such as an internal server or a database) available to applications running on the platform. | Networks |
| Share | A directory exposed over HTTPS and WebDAV so users can browse and edit files in a browser or file manager. | Shares |
| SSH | A secure shell service exposed so users can connect with their SSH client. | SSH |
| Template | A reusable file template (for example a document template) that users can request or download. | Templates |
%%{init: {"theme": "base", "themeVariables": {"background": "#ffffff", "primaryColor": "#e8f1fb", "primaryBorderColor": "#1f4e79", "primaryTextColor": "#111111", "lineColor": "#4a4a4a", "secondaryColor": "#f5f5f5", "fontFamily": "Inter, sans-serif"}} }%%
flowchart TD
RES[Resources]
RES --> APP[Application<br/>browser access]
RES --> DESK[Desktop<br/>remote desktop gateway]
RES --> SH[Share<br/>HTTPS / WebDAV files]
RES --> DB[Database]
RES --> SSH[SSH service]
RES --> NET[Network]
RES --> LAUNCH[Launcher]
RES --> TEMPL[File template]
RES --> CONN[Connector]
What every resource shares
All resources share the same access model:
- Name and address. You give the resource a name and tell the platform where it lives (a hostname or IP and the ports to expose).
- Connector. The resource is reached through a connector at your site.
- Permissions. You grant users, groups, and service accounts access to the resource, down to a specific role or read/write level. See Resource permissions.
- Policies. Rules such as geolocation restrictions or firewall rules apply to the resource. See Policies.
- Labels. You can attach labels to organise resources and drive permissions and policies. See Labels.
- Audit. Every access attempt is recorded.
How a resource is created
Every resource type has a creation wizard in the portal. Although the steps differ, the shape is the same:
- Choose the connector the resource is reached through.
- Name the resource (a valid hostname).
- Give the address: the hostname or IP and the ports.
- Configure advanced options (TLS, protocols, overrides) if needed.
- Review and apply the summary.
- Done: the resource is created, and you can assign permissions, add it to resource groups or policies, or add it to resource groups for management.
After creation you can:
- assign permissions (see Resource permissions);
- add the resource to a resource group;
- attach labels;
- apply policies; and
- monitor access through audits and metrics.
Resources overview
The Resources overview page lists everything in your organisation by type and lets you jump to each resource’s management screens. It is the central place to understand what is exposed and through which connector.