Thanks a lot for the responses, guys. Sorry I couldn’t get back sooner.
So, my reasoning behind thinking I shouldn’t use the users collection is simply that I was struggling to customize it. I should mention that I’ve been using the useraccounts package by splendido in my initial attempts to get this working the way I want it to, and it is very easy to customize the UI, and not provide a registration option, etc… (There is also a version of useraccounts styled for meteor-ionic, which is the framework I’ve chosen to go with, so it’s great.)
But, like I said, I was having a hard time figuring out how to customize the users collection to fit my needs. I added a new field via my Mongo GUI tool (MongoVue), but I couldn’t access or even find that field from within the application. So, I figured it would just be easiest to create my own accounts system with my own custom collection that I could make to match the external collection that the owner of the app will be using to register new users, if that’s what I needed to do.
HOWEVER, after talking it over with one of my partners on this project yesterday,
it looks like we are electing to actually offer the registration button to new users because we want them to generate their own password from the start, as well as their username. So, we’ll also be trying to stick with the normal users collection. (Which it looks like you guys were going to convince me to do anyway .)
Our thinking is that, before being able to use the app, the user has to have been approved by the app owners, which has always been the case. After the user has applied and been approved, they will have an email on file with the owner, which we will store as part of a separate userprofile collection. Upon registration, we need to check that the email the user is attempting to register with is present in our userprofile collection, and that it doesn’t have a password attached to it, meaning nobody has registered with that email yet. Otherwise, the registration fails. This way once the user is registered, we can grab a manually assigned ID in that userprofile collection whenever they log in that will be used to grab all of the appropriate data/content for them.
Does this sound like a good approach?
Does it sound easily achievable?
Are there any obvious obstacles I’m overlooking?
Sorry to give you so much to read. I got really excited when I came back and saw your responses. Thought I should be as thorough as possible.
Thanks again for any help.