You can make learning objects available to users who do not have IDs and passwords for Learning Environment. This is beneficial if you want to open the learning object to metadata harvesting. When you create a new object, or edit an existing one, you can choose whether to make it externally available.
Users outside Learning Environment cannot see object files or details for a publicly available learning object.
External availability requires the D2l.tools.LOR.AllowExternalAvailabilityEdit configuration variable.
If you want to make learning objects that are currently secured into ones that are publicly available, the best practice is to always grant the ability to view objects in the repository at the org level. This specifically affects learning objects published from the course level and accessed through deep linking (i.e., users not signed into Learning Environment click a link to view a learning object and are prompted to sign in to access it).