> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a project

> Choose the source language, target languages, and scope for a native Platform project.

Create a project for content that shares a source language, language resources, and review workflow. A website, mobile app, or documentation set can each have its own project.

## Before you start

Choose the source language actually used in your files and at least one target locale. You need permission to create projects; contact your administrator if the create action is unavailable.

## Create the project

1. Open **Projects** and start a new project.
2. Enter a **Name** your team can recognize.
3. Add a **Description** for scope, ownership, or release notes.
4. Choose the source locale and target locales. The source locale cannot also be a target.
5. Select **Save project**.

Open the project and confirm its language settings before uploading content. Use separate projects when content needs different source languages or access boundaries.

## Native and connected projects

In a native project, upload and manage source files in Platform. In a project backed by a TMS, browse the provider’s files and manage provider-owned language settings there. Check **Settings** → **Source connection** if you are unsure which kind you opened.

## Next

[Manage project languages](/platform/projects/languages), [upload files](/platform/projects/files), and [add project guidelines](/platform/knowledge/guidelines).

Compare [native and connected TMS workflows](/platform/tms) before choosing your project's content owner.