# Getting started

## Build a new use case

In this tutorial, we will use the Use Cases application to create a new use case with a variety of application and Ontology resources. We can then navigate to applications like Workshop and Ontology Manager directly from the use case overview page, as well as add additional applications.

## Part 1: Create a use case

First, we need to access the Use Cases application.

When logged into Foundry, access the Use Cases app from the left-side navigation bar under **Platform Apps**. If the application is not visible, select **View all** and find **Use Cases** under the **Operational applications** section of the **Platform apps** search window that appears.

You will now be on the home page of the Use Cases app. This page will be empty if you have not yet created a use case.

In the right side of the **All use cases** section, click **+ Create new**. This will open the **Create use case** modal. Add the use case name and description. In our example, the use case name is “Flight alert use case”, and the description is “Use case for managing flight alerts and updating schedules."

![Create use case modal](../../../assets/c23f2cef1ea27a542e0b15a7bcefe2cf3fa7d5fb5e89813d0dabf791bf8a6962.webp)

In this tutorial, we will create a new backing Project in the filesystem. Click **+ Create new** in the bottom right corner to open the **Create new project** modal that will allow you to add a new Project to your Foundry filesystem. Add a name, optional description, and [space](../../platform-security-management/manage-orgs-and-spaces/index.md#spaces) for your Project.

Your space will determine the default Organization and role for users in your Organization. In our example, our Project is named “Flight Alert Project” with the description “Backing Project for Flight Alert use case”. Our space is `Palantir`, our Organization is `Palantir`, and the default role is `Viewer`.

![Create new Project modal](../../../assets/ef1faaf1e9e1eeb0fbce495029787698abc34ce2eac2481ac4a3c899cd24eb1c.webp)

Select **Create** to create the new Project and return to the **Create use case** modal. Select **Create** again to create your use case and enter the [use case overview](../use-case-overview/index.md) page.

Learn more about [Organizations](../../security/orgs-and-spaces/index.md), [roles](../../security/projects-and-roles/index.md), and other [platform security](../../security/overview/index.md#platform-security) concepts.

## Part 2: Edit metadata

After creating your use case and backing Project, you can modify the metadata that helps define your use case. This metadata includes the use case name, description, owners, and status.

At this point, your use case overview should look like this:

![An example use case overview page in an empty state](../../../assets/b623a4235a96409c712685be295bb61c22e4bd344872b7dafd733cf3e083233e.webp)

You will be the technical owner of the use case by default. In our example, we are using a `test` user.

### Name

If you want to change the name of your use case, you can do so from the use case overview page. Click on the use case name at the top of the page and edit within the text field.

![Rename the name of your use case](../../../assets/10db9435f19577e0f5944a2a6606187387f43017e00cdedf883c4d2fb7f07a67.webp)

### Description

You can easily change the description of your use case by clicking on the description and editing within the text field.

![Modify use case description text](../../../assets/b5abe130867ec50da052c6e5295ed99a226a2e8d3c1fe10ad1b6f1caffa7bf4c.png)

### Owners

There are two types of owners that you can assign to your use case: **Technical** and **Business**.

* **Technical owner:** The technical owner is generally the application builder who is responsible for using Foundry resources to create application outputs for the use case.
  * You are the default technical owner of your use case.
* **Business owner:** The business owner is typically a user who tracks workflow progress and financial details of a use case.
  * There is no default user assigned as a business owner to your use case.

To change the owners of your use case, hover over the name or empty field and click on the pencil icon. This will open a search dropdown where you can scroll through or search for available users. As we do not yet have a business owner for our use case, we will assign one now.

![Use case with only a technical owner assigned](../../../assets/e5b56f851999db805d220c939bf03c3e6ca26ccb77165802a7bfa1ba40a92add.webp)

We added user `test2` to be the business owner of our use case.

![Use case with both a technical and business owner assigned](../../../assets/968408d06b4cc84c9de503fbd011f398b6335e4ef7d615288ae69f37a3f5b3a8.webp)

### Status

You can assign your use case a status relevant to its operation status:

* **Active:** Published and operating within your Foundry instance.
* **Experimental:** In-progress and not actively published.
* **Deprecated:** No longer in operation.

Change the status of your use case from `Experimental` to `Active`. Click on the status dropdown, choose `Active`, then click **Change status**.

![Choice of status labels for use case metadata](../../../assets/44fbdcc9e8089984ddfc2b4b218fd0f0a94e2c3549cdbec294ac983c255f61c4.webp)

## Part 3: Add resources

Now that we have created a new use case with a backing Project, we can begin adding application resources. Start by creating a new Workshop module.

From your use case overview page, find the **Applications** section in the middle and click **+ Add new application**. Choose the Workshop option, then click **Create**.

![Create new application modal](../../../assets/42258a1e4b4a63ee88e1a5ec4000e33c0761b90d0b436f3ab7a16a6f5647b9cd.webp)

The new workshop module will be created and opened. From here, you can name the module and choose from various widgets to configure and use. Learn more about [creating interactive modules](../../workshop/overview/index.md) in Workshop.

You can [navigate back](../navigation/index.md#navigation-between-foundry-applications) to the use case by clicking the top left header of the Workshop module name.