Say there is an online hotel management application. One feature is the Receptionist will confirm and cancel bookings made by the customer. So all Receptionists do the same things. Is it bad practice to add a single row to the database representing all the Receptionists in the hotel then let them access it to login to the site? For example:
table Receptionist RecID primary key, username, password
Then only one insert:
insert into Receptionist values('rec','rec');
now, rather than each Receptionist having records of their own so they can login, all of them will just use this account to login. What's the benefit for having one row for each in this case? I'm thinking security, are there any others?