The user who imports an asset into the consumption registry specifies the organization into which asset will be imported. This user can import the asset to any organization for which he or she has Create Assets permission. If the archive file includes system-wide objects, such as asset types or taxonomies, the user who performs the import must also have permission to create those types of objects. Because of the permission requirements that an import process might require, an administrator in the CentraSite Administrator role often performs the import task. (Bear in mind, that whoever imports the objects on the target registry becomes the owner of those objects. For this reason, you might want to have more than one user in a role with the permissions necessary to import all types of registry objects.)

Be aware that when an asset reaches an end state on a particular stage, the asset remains in that end state on that stage regardless of the state changes that occur in the next stage. For example, when a schema reaches the Promotion state in the example above, the schema's state will no longer change on the creation registry. The remaining states in the schema's overall lifecycle (that is, the Available, Deprecated, Retired states), are reflected only in the consumption registry. To determine whether a Promoted schema has been moved to the Deprecated or Retired states, a user must view the asset in the consumption registry.