Namespaces for Second-Generation Managed Packages

A namespace is a 1–15 character alphanumeric identifier that distinguishes your package and its contents from other packages in your customer’s org. A namespace is assigned to a second-generation managed package (managed 2GP) at the time that it’s created, and can’t be changed.

When creating a namespace, use something that’s useful and informative to users. However, don’t name a namespace after a person (for example, by using a person's name, nickname, or private information).

Important

When you work with namespaces, keep these considerations in mind.

You can develop more than one managed 2GP package with the same namespace but you can associate each managed 2GP package with only a single namespace.
If you work with more than one namespace, we recommend that you set up one project for each namespace.

When you specify a package namespace, every component added to a package has the namespace prefixed to the component API name. Let’s say you have a custom object called Insurance_Agent with the API name, Insurance_Agent__c. If you add this component to a package associated with the Acme namespace, the API name becomes Acme__Insurance_Agent__c.

Second-Generation Managed Packaging Developer Guide

Namespaces for Second-Generation Managed Packages