|Manuals

Access Profiles and Cloud Manager

Access Profiles are the bridge between Thinfinity® Cloud Manager and end users. A VDI/DaaS model defines the infrastructure to provision on demand; a Managed VMs connection links to VMs that already exist. In either case, an Access Profile defines who can use the target and how they connect. Without an Access Profile, instances managed by Cloud Manager are invisible to users — they exist on the cloud provider but cannot be reached through Thinfinity® Workspace.

Access Profiles are a core Thinfinity® Workspace feature, not a Cloud Manager feature. An Access Profile is the entry point through which a Workspace user reaches a Cloud Manager target — a model or a Managed VMs connection. The scope of this article is that integration: the Cloud Manager-specific configuration in the Access Profile editor, and the connection flow it enables.

Info

For full Access Profile documentation, see Understanding Access Profiles in the Thinfinity® Workspace product manual.

Connection Paths

Access Profiles support three distinct integration paths with Cloud Manager, mirroring the three infrastructure paths documented under Concepts.

Path Use When Procedure
Managed VMs The user connects to specific, named VMs that already exist (managed by Cloud Manager but not provisioned by it) Create an Access Profile for Managed VMs
VDI/DaaS Model The user connects to a pool of dynamically provisioned instances backed by a model Create an Access Profile for a VDI/DaaS Model
Kubernetes Model The user connects to a pod scheduled by the cluster from a K8S model Same Access Profile editor; the linked Cloud Manager target is a K8S Model. Pod selection and lifecycle are governed by the cluster.

The three paths use the same Access Profile editor.

Connection Flow Overview

When a user opens Thinfinity® Workspace and clicks an Access Profile bound to Cloud Manager, the following sequence runs:

1. User selects Access Profile in Workspace
       │
       ▼
2. Workspace looks up the linked Cloud Manager target
   (a Managed VMs connection, or a VDI/DaaS Model)
       │
       ▼
3a. (Managed VMs)             3b. (VDI/DaaS Model)
    Cloud Manager checks         Cloud Manager finds
    that the named VM            an available instance
    is reachable                 (assigned, standby, or
                                 newly provisioned)
       │                            │
       └─────────┬──────────────────┘
                 ▼
4. If the target VM is powered off, Cloud Manager powers it on
                 │
                 ▼
5. Workspace establishes the session via the configured Connection Mode
   (Public IP, Private IP, or Agent Id)
                 │
                 ▼
6. User receives the desktop or application session

For the user-facing details of this flow, see Connect to an Instance.

Cloud Manager-Specific Configuration in the Access Profile

Most of the Access Profile editor’s sections (Display, Resources, Program, Experience, Advanced, Desktop Client, Access Hours, Permissions, Authentication Methods, Restrictions) are standard Thinfinity® Workspace features documented in the Thinfinity Workspace product manual. Two sections expose Cloud Manager-specific configuration.

General — Cloud Manager Source

At the top of the General section, two paired controls bind the Access Profile to a Cloud Manager target:

Control Description
Source type Selects between VDI/DaaS Models and Managed VMs.
Target picker Selects the specific VDI/DaaS model or Managed VMs connection. The dropdown lists each item with its internal identifier.

When the source type is Managed VMs, an additional toggle appears in the General section:

Toggle Description
Use Instance When enabled, an Available instances dropdown appears listing the VMs currently tracked under the selected Managed VMs connection. Selecting an instance pins the Access Profile to that specific VM. When disabled, the broker selects an instance at session time.

When the source type is VDI/DaaS Models, an additional toggle appears in the General section:

Toggle Description
Use Staging When enabled, the Access Profile targets the Staging version of the selected model instead of Production.

Resource Reservation

The Resource Reservation section enables optional booking for VDI/DaaS Access Profiles — users reserve a time slot before connecting rather than being assigned an instance on demand.

Field Description
Booked access only Master toggle. When on, the profile is bookable; when off, it accepts direct connections without reservation.
Allow booking for Dropdown that controls who can make reservations: Attendees, Organizers, or Organizers and Attendees.
Booking limit Maximum number of concurrent active bookings allowed for the Access Profile.
Buffer Lead time (minutes) before each reservation that Cloud Manager pre-warms the target instance.
Organizers List of users granted the Organizer (Approver) role on this profile.

For the full Resource Reservation feature reference, see Resource Reservation.

Permissions

The user opening an Access Profile must have permission to do so. Permissions on Access Profiles are managed through Labels and the Permissions tab of an Access Profile Editor. For details, see Access Management in the Thinfinity Workspace product manual for details.

For administrators creating and editing Access Profiles, the Manage Profiles permission grants the necessary access. It is configured in the Permissions tab of Thinfinity® Configuration Manager — see the Enable Cloud Manager / Cloud Manager Permissions section.

What’s in This Section

Page Description
Create an Access Profile for Managed VMs Step-by-step procedure for the Managed VM path
Create an Access Profile for a VDI/DaaS Model Step-by-step procedure for the VDI/DaaS path
Connect to an Instance End-user connection experience
Resource Reservation Optional booking integration for VDI/DaaS Access Profiles

See Also