These options can only be setuped in the backend.
Choosing a generic mail or/and password make things easier because, for example:
I want to consider all new users as books.
1-I add the name (here the title of the book) and register
If the book exists, with the checking of no double name option, I'll know that he's already existing in database.
2-When register, I automaticaly login, so I can add all text, images etc...related to the book.
3-Then I logout
4-Then I see an error on the book description.
5-I need to login again, but I can't remember the password...I may have registered with a generic one ( 123456) but, I (or something else using the system) may have entered a wrong password (like 134256 )
Of course as administrator I may edit the profile, but I don't want to allow other users with so much rights.
In that case I may also log anything related to THAT user(or book...)
I also may add specific options only to that user ( a calendar event for example for that book, I can't do that with the publisher profile who could edit the content...)
So a generic mail and password, will help to make checking faster, and without possible mistakes.
I think it's clearer now, if not let me know
