---
schema_version: "1"
id: 23e4811bde630c67b1b87fc386e4818b9521082c646ba0eca246bb4739fcaabe
title: Component Namespace
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/namespaces/namespaces-intro.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/namespaces-intro.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: a37ae1098b240b95d56a1991ad0bd73c16b2ebbbe4fd86bb872ba604715792af
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# Component Namespace

Every component is part of a namespace, which is used to group related components together. If your organization has a namespace prefix set, use that namespace to access your components. Otherwise, use the default namespace to access your components.

Another component or application can reference a component by adding `<myNamespace:myComponent>` in its markup. For example, the `helloWorld` component is in the docsample namespace. Another component can reference it by adding `<docsample:helloWorld />` in its markup.

Lightning components that Salesforce provides are grouped into several namespaces, such as `aura`, `lightning`, and `force`. Components from third-party managed packages have namespaces from the providing organizations.

In your organization, you can choose to set a namespace prefix. If you do, that namespace is used for all of your Lightning components. A namespace prefix is required if you plan to offer managed packages on the AppExchange.

If you haven’t set a namespace prefix for your organization, use the default namespace `c` when referencing components that you’ve created.

## Namespaces in Code Samples

The code samples throughout this guide use the default `c` namespace. Replace `c` with your namespace if you’ve set a namespace prefix.