App Collection

An App Collection workspace presents a set of application tiles. Users launch only the applications you assign, each in its own streamed window — without exposing a full desktop. This is the most common workspace type for delivering line-of-business applications.

Prerequisites

The application you want to present must already be published (Applications), and the group you want to grant must already exist (Groups). The Add dialogs on the workspace only list existing published apps and existing groups.

Create an App Collection

Creating a workspace has two parts: the create form, then two tabs on the workspace's own detail page. Applications and groups are not assigned on the create form — you add them afterwards.

1. Fill in the create form

  1. Open Workspaces and click Add Workspace.
  2. Name the workspace.
  3. Type: select App Collection.
  4. Policy Set: the dropdown defaults to None (use organization default) — select the policy that matches the sensitivity of the applications.
  5. Turn ON Published (visible to users) (off by default), then click Create. You land on the workspace detail page with Applications and Access Rights tabs.

2. Add applications (Applications tab)

  1. On the Applications tab, click Add Application.
  2. Select an application in the dialog and click Add. At least one is required. Repeat for each app.

3. Grant access (Access Rights tab)

  1. Switch to the Access Rights tab and click Grant Access.
  2. Select a group (for example everyone or a specific group) and click Grant Access. Every member of that group then sees the workspace at login.
A streamed application from an App Collection running in the browser.
Nothing is auto-assigned

After you click Create, the workspace has no applications and no access rights. If you stop there, no user can launch it. You must add at least one application and grant at least one group on the two tabs, and the workspace must be Published.

Tip

App Collections give the tightest control: users see only the applications you publish, not the underlying desktop. Prefer them over a full desktop unless users genuinely need desktop-level access.