A package user is automatically registered when the user is successfully authenticated by the security configuration mapped to the MBO package. This is the identity used by the application to synchronize with the MBO package. The same identity is also registered as application user for native replication or messaging applications.
Package users are automatically removed when packages are removed. Those users can also be manually removed by an administrator. Typically, the administrator does the clean up to release server-side resources when the package user is no longer an active user of the MBO package. Removal of package user deletes subscription(s), server-side personalization data, cached data, and other internal artifacts associated with that user. Once the package user is removed, the device application for that user will not work until the user takes actions in the application that result in recreating the local database, synchronizing, and so on. If a user happens to be the last package user from that device, removal of that user would also result in freeing up of the device license consumed by that device.
When Unwired Server is upgraded from a previous release (such as 2.0 or 2.0.1), with MBO packages deployed to it, package users entries are automatically created for the packages on behalf of users already-registered for those packages.