Understanding Access Profiles

An Access Profile is a core, customizable component of Thinfinity® Workspace. This entity, created by an administrator, encapsulates user connectivity and interaction parameters essential for establishing connections to remote resources, such as applications, virtual machines, desktops, isolated browsers, and file repositories. Depending on the specified connection type, it utilizes the appropriate communication protocol corresponding to each endpoint resource. Additionally, it defines access permissions and configures user experience settings for members (groups and individual users).

Access Profiles function as mechanisms for securely publishing and provisioning remote resources to end-users. The creation process executes sequentially through the Access Profile Wizard, which streamlines the configuration of essential parameters required to establish secure, reliable, and functional remote connections.

Access Profiles can be managed from a dedicated tab within Thinfinity Workspace Web Manager, which facilitates creation, modification, and deletion of profiles. For a comprehensive description of all the parameters available for Access Profiles, navigate to the Access Profiles section of this manual.

Public and Private Access Profiles

Access Profiles in Thinfinity Workspace are classified as either public or private, depending on who creates and manages them. Public Access Profiles are created by administrators or users with the Manage Profiles permission. They are organizationally governed resources, subject to the full set of Access Profile Policies and managed through the administrative Apply/Discard workflow. Visibility and access are controlled through per-profile permissions and collectively through Label-based permissions.

Private Access Profiles are created by end users for their own use. By default, a private profile is visible only to its creator, but the creator can choose to make it accessible to other users — either to all authenticated users or to a selected set of users and groups. Private profiles use a simplified permissions model and are managed directly by the creating user, outside the administrative Apply/Discard workflow.

The distinction between public and private profiles reflects a difference in access governance rather than in connection capability. Both types support the same range of connection types and session features. What differs is who provisions the access, who controls the authorization decisions, and what level of organizational policy oversight applies.