> 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/before-you-begin.md).

# Before You Begin

Before creating your first DC Works Applet, make sure you have access to the required account, tools, and runtime environment.

### What you will need

To complete the Getting Started tutorial, you will need:

* A DC Works user account.
* Access to the web-based DC Works Designer.
* Permission to create or modify Applets, Suites, databases, and tables.
* A licensed Android device running DC Works, or access to the DC Works Web App through a compatible browser.
* An internet connection for designing, publishing, and synchronizing your solution.

Your organization’s DC Works administrator can provide access and confirm which permissions and licenses have been assigned to you.

### Choose how you will run DC Works

DC Works solutions can be used in two ways:

#### Android application

Use the DC Works Android application on a compatible Android device. This is generally the preferred option for mobile data-collection workflows involving barcode scanning and other device-specific capabilities.

#### DC Works Web App

Use the DC Works Web App to run Suites and Applets through a compatible web browser. This allows DC Works solutions to be used on PCs, Apple devices, and other supported platforms without installing the Android application.

{% hint style="info" %}
Some hardware-specific features, such as integrated barcode scanner controls, may depend on the device and the method used to run the Applet.
{% endhint %}

### Required permissions

The features available in the DC Works Designer may depend on your assigned role and permissions. For this tutorial, your account should allow you to:

* Create and edit a database and table.
* Create and edit an Applet.
* Create and edit a Suite.
* Add an Applet to a Suite.
* Make the Suite available for testing.
* Access the Suite from your chosen device or browser.

If an option described in this guide is unavailable, contact your DC Works administrator to verify your permissions.

### Plan your first Applet

Before opening the Designer, identify the basic information your Applet needs to collect.

In this tutorial, we will create a simple **Asset Check-In Applet** containing the following fields:

| Field                  | Purpose                                                 |
| ---------------------- | ------------------------------------------------------- |
| Asset ID               | Identifies the asset, manually or by barcode            |
| Employee or Location   | Records who returned the asset or where it was received |
| Check-In Date and Time | Records when the asset was checked in                   |
| Condition              | Records the condition of the returned asset             |
| Notes                  | Captures any additional information                     |

This example introduces the basic DC Works workflow without requiring programming experience.

### Next step

Continue to **Sign In and Explore the Designer** to access DC Works and become familiar with its main areas.


---

# 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/before-you-begin.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.