Preserve the timing
Record which profile was used before and after the change and whether the underlying media storage remains available. Do not delete the apparently empty library as a first step. Return through the supported interface to the known original profile and inspect the same authorised source. Confirm one known file remains in its original storage location without modifying it.
A hypothetical household example is creating a fresh profile without copying the original sources. The new view may reasonably contain less information. That does not establish that the older profile’s data or the media files were removed.
Inspect current settings carefully
Use the installed Kodi version’s profile interface to review what should be shared. The older concepts page explains the distinction, but it also contains obsolete version-specific troubleshooting. Do not copy old scripts or edit profile XML merely because a menu looks unfamiliar.
Write the intended arrangement: independent media state, shared information or another supported option. Check one known permitted title after a deliberate change. Keep the original Kodi data backup available so a profile experiment remains reversible.
Keep privacy at the proper layer
Kodi’s concepts page says profiles are not a security feature. A source absent from one profile’s ordinary view is not a guarantee of protected access against another user. Use appropriate system or server access controls for private media instead of relying solely on presentation.
For support, include Kodi version, profile names, expected sharing and the exact view that differs. Hide credentials and private paths. If the original profile is also empty and storage is missing, record that separate result. The goal is to establish context before interpreting a changed interface as lost data.
