# App library

## Manage Apps across Timebook

One of our key goals is to provide all the tools you need to manage your work in one place. Timebook offers multiple modules to help you with all aspects of work management. We call these modules "Apps", and you can build them using this section of Workplace Admin.

If you don't want to spend time building Apps, you can also use the default ones, which you get out-of-the-box with Timebook. We have dedicated Apps where you can manage work in a classic way, using Goals, Initiatives, and Work Items. And you can still customize our default Apps if you need to modify their contents.

{% hint style="info" %}
The App library has a middle pane that lists all the Apps in [your Workplace](#user-content-fn-1)[^1].

See the rest of this article to learn more about editing and creating Apps in the library.
{% endhint %}

***

## Edit an App

You can use the App library to edit any App in your Workplace. First, select an App from the middle pane and start making changes in the main working area.

The working area of the App library has two sections:

* The \[**Item types**] section helps you define which item types are allowed in your App. You can add item types using \[**+**] at the top or remove them using \[**Trash bin**] next to a particular item type. In short, this section helps you build an App that allows only a few selected types of items to ensure the contents match the App's purpose.
* The \[**Containers**] section helps you define the containers for storing items in your App. With containers, you can group items and track them with less effort. Projects and Sprints are examples of containers, as you can add multiple items to a singleProject or Sprint. You can add containers using \[**+**] at the top or remove them using \[**Trash bin**] next to a particular container.

{% hint style="success" %}
We have added the \[**Hierarchy**] button next to the \[**Item types**] section.

You can use it to define the parent-child relationship between item types in your App.

In short, the hierarchy screen lets you decide which item types can be assigned as "parents" to which other item types. For example, you might want only the "Epic" item to be available as the parent for the "Task" and "Story" items.
{% endhint %}

{% hint style="info" %}
As item types are crucial in managing your App, we suggest you read the article about managing item types in Timebook. For more information, see <mark style="color:red;">**ITEM LIBRARY LINK**</mark>
{% endhint %}

***

## Create an App

You can create custom Apps if you are not satisfied with the Timebook default ones:

1. In the middle pane, press \[**+**] at the top of the list.
2. Give your new App a meaningful name and description.
3. Your new App is added to the list of Apps. Select it and start editing its contents. The previous section of this article provides information on how to edit an App.

{% hint style="info" %}
To delete an App or edit its name and description:

1. Select an App from the list in the middle pane.
2. Press the \[**Meatballs**] icon in the top-right corner.
3. Select \[**Edit**] and make your changes or press \[**Delete**].
   {% endhint %}

***

## Related articles

[^1]: A Workplace is the top-level administration unit in Timebook. It is a mirror image of your organization, representing all the people grouped in Teams and working together using shared resources.

    For more information, see [https://github.com/TimebookDev/gitbook-prod/blob/master/settings/workplace-settings/broken-reference/README.md](https://github.com/TimebookDev/gitbook-prod/blob/master/settings/workplace-settings/broken-reference/README.md "mention")


---

# Agent Instructions: 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:

```
GET https://help.timebook.ai/hc/product-guide/workplace-settings/app-library.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.