Registering a namespace is a one-time action you take on a dedicated Developer Edition org before you build a managed package. Pick the prefix with care, because it is permanent once confirmed.
- Create a clean Developer Edition org
Sign up for a fresh Developer Edition org reserved for packaging. Do not reuse a sandbox, a production org, or your Dev Hub org for this. The org you choose becomes the long-term home of the namespace.
- Open the namespace registration screen
In Setup, enter Package Manager in Quick Find and open it. If no namespace is registered yet, the page shows an option to register one. Start there.
- Enter and check a candidate prefix
Type a one-to-fifteen-character alphanumeric prefix that reflects your company or product. The platform checks availability across AppExchange in real time and rejects any value already taken.
- Review and confirm
Confirm the prefix only when you are certain. After you save, the namespace is locked to this org and applied to every packaged component, with no option to rename or transfer it later.
One to fifteen alphanumeric characters, case-insensitive, that begins with a letter and is unique across AppExchange. This becomes the prefix on every component in the package.
The dedicated org that owns the namespace. For 1GP this is your packaging org; for 2GP it is a namespace org linked to your Dev Hub.
- The prefix is permanent. You cannot rename, transfer, or reuse a registered namespace, so test candidate names against your branding before you confirm.
- You cannot register a namespace on an org that already contains a managed package, which is one more reason to use a fresh Developer Edition org.
- Cross-package references break if you omit the prefix. Code that worked unprefixed inside the packaging org must use namespace.Class or namespace__Object__c once called from a subscriber org.