Talk:Computer Operations/sandbox

Rob, you have listed that the passwords should never have to be changed. Why? If anything is going to change frequently, that'll be it. Members of course should change it and I can set it so that when a CC member does it, it's a reset with a notice going to the member that their password is reset and give them the new password.

Also why do we want to allow branch heads to promote? Are we giving them the ability to promote over a CO's head? Not a problem for me per se' just making sure we want to.

I think joindate and username are two items we should not set as easily cahngeable even by the CC. Joind date should be something that never changes. The odd mistake can be changed in the raw DB. short of a marriage, the same principle works for the username.

Logan

---

Passwords:	Just spitballing on that. I've never had to change mine. If you forsee people needing to change passwords frequently... NP here
Promotions:	Simple... Past Practice. We've allowed Branch Heads to promote their members up to and including Capt/Col before. If their CO is only an LCDR/LCOL then the CO needs to bump himself up! (Grin)
Joindate/ Username:	Right... Since you lumped Membership and CC together, I did mark that they should be the only ones to input Joindate. I did mark "2" for Username... but Marriage & Legal Name Change is what I had in mind. If you don't want them to have access to that... NP.

Rob