Every user who plans on accessing the LMS will need an account. You can set them up with a minimum amount of data and/or allow self-registration depending on your business model.

​@ryanmalott - ​@lrnlab has a perfect point - self registration can really help you hear and keep your effort minimal with a set it and forget it type of approach. If you have concerns about security, you can go further and make the user enter a branch code that you supply to them.

We use a high level branch structure that was recommended at implementation to support externals. The stuff below it is not too important and is in my company’s name / language / business. But high level we pump these folks you are describing to our external branch.

We occasionally have outside consultants that need access to some, not all, of our courses.

We know the user info and the courses, so we import the users and use the enrollment import as well.

Then we have a default menu and page set up for these types of users that has a welcome message on the top and then ONLY shows the courses they are enrolled in. 

Direct and to the point.

We also typically, but not always, have an expiration date tied to the user...keeping that maintenance easier as well.  Hope that helps.