> For the complete documentation index, see [llms.txt](https://docs.amltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amltd.com/dc-works/getting-started/create-a-suite.md).

# Create a Suite

A **Suite** groups one or more Applets into a launcher that can be assigned to Web Users or Device Users.

In this guide, you will create a Suite named **Getting Started** and add the **Asset Check-In** Applet created earlier.

### Start a new Suite

1. Select **Suites** from the left navigation menu.
2. Select **Create Suite +**.

<figure><img src="/files/iR0rsSwznk57do1S8WbM" alt=""><figcaption></figcaption></figure>

*Select Create Suite + to begin creating a Suite.*

### Choose a Suite template

The template window displays the available Suite launcher layouts.

For this tutorial, select:

**Blank Launcher (Dark, Small Icons, Logo)**

<figure><img src="/files/lCW5Nohva5s4ZrX7JEqf" alt=""><figcaption></figcaption></figure>

*Choose the Blank Launcher template with a dark background, small Applet icons, and a logo area (the first template, upper left).*

This template creates a dark launcher screen with:

* A company logo at the top
* Small buttons for opening the included Applets
* Space for adding more Applets later

After selecting the template, its configuration form opens.

### Configure the Suite

In **Suite Name**, enter:

`Getting Started`

The Suite-creation form also provides the following settings:

| Setting                | Purpose                                                                                                |
| ---------------------- | ------------------------------------------------------------------------------------------------------ |
| **Require User Login** | Requires the user to authenticate before accessing the Suite.                                          |
| **Offline Support**    | Allows supported Suite functions to remain available when the device temporarily loses its connection. |
| **Auto Update**        | Allows the Suite to receive available updates automatically.                                           |
| **Logo**               | Uploads a logo displayed on the Suite launcher.                                                        |
| **Applications**       | Selects the Applets included in the Suite.                                                             |

For this tutorial:

* Name the Suite **Getting Started**.
* Leave **Require User Login** cleared.
* Leave **Offline Support** selected.
* Leave **Auto Update** selected.

<figure><img src="/files/RNBLyWFFVkWXW9rxOI1b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The appropriate login and offline settings depend on how a Suite will be used and the type of information it handles. These options will be explained in greater detail elsewhere in the documentation.
{% endhint %}

### Select a logo

Under **Logo**, select **Upload** and choose the image that will appear at the top of the Suite launcher.

The selected template includes a designated area for this logo.

### Add the Applet

1. Open the **Applications** list.
2. Select **Asset Check-In**.

<figure><img src="/files/3gA5RMkicUWlmQLSKB0r" alt=""><figcaption></figcaption></figure>

*Add the Asset Check-In Applet to the Getting Started Suite.*

A Suite can contain more than one Applet. For this introductory tutorial, only the Asset Check-In Applet is required.

### Create the Suite

Review the Suite name, options, logo, and selected Applet. Then select **Create**.

DC Works creates the Suite and opens it in the **Suite Designer**.

<figure><img src="/files/r1RWSqICoO8Mh1eld5MM" alt=""><figcaption></figcaption></figure>

*The newly created Getting Started Suite contains a button for opening the Asset Check-In Applet.*

The Suite begins at revision **v1.00** and contains:

* The uploaded logo
* An **Asset Check-In** Applet button
* The selected launcher background and layout
* The settings selected during creation

At this stage, the Suite has been created but should still be reviewed, saved, and tested before being assigned to users.

### Next: Review the Suite structure

The next portion of this guide will explain the Suite Designer, including:

* Suite fields and Applet buttons
* Suite properties
* Layout and background settings
* Applet button positioning and appearance
* Suite actions
* Saving and testing the Suite


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amltd.com/dc-works/getting-started/create-a-suite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.