---
schema_version: "1"
id: d1d15123c17f2f143149f2ae674570062377ec365c4a35626f8326845ad0b0d5
title: Creating a Namespace in Your Organization
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/namespaces/namespaces-creating.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/namespaces-creating.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 954ffb1bf580beac45251e8534346ba08cbcfe1b3ad62378524e4871c2a5e966
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# Creating a Namespace in Your Organization

Create a namespace for your organization by registering a namespace prefix.

If you’re not creating managed packages for distribution then registering a namespace prefix isn’t required, but it’s a best practice for all but the smallest organizations.

Your namespace must:

-   Begin with a letter
-   Contain one to 15 alphanumeric characters
-   Not contain two consecutive underscores

For example, `myNp123` and `my_np` are valid namespaces, but `123Company` and `my__np` aren’t.

**note:** To register a namespace in an org, use a Developer Edition org that’s separate from your Dev Hub or scratch orgs.

To register a namespace:

1.  From Setup, enter `Package Manager` in the Quick Find box and select **Package Manager**.
2.  In the Namespace Settings panel, click **Edit**.

    **note:** After you’ve configured your namespace settings, this button is hidden.

3.  Enter the namespace you want to register.
4.  Click **Check Availability** to determine if the namespace is already in use.
5.  If the namespace prefix that you entered isn’t available, repeat the previous two steps.
6.  Click **Review**.
7.  Click **Save**.

Next, you can [link the namespace to a Dev Hub org](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_reg_namespace.htm), which you can use to manage scratch orgs and build second-generation packages (2GP) for distribution.