Login & User Management

Anything related to User Roles, Logging in & Resetting Passwords

Technical Notes

Roles

• X1 —> root codes

• E —> evaluators (same login, + pins)
  • can read and evaluate applications
  • All Evaluations have the same logins, but the comms table will usually cover the PIN codes for each of the Evaluators

• G —> NGOs

• J —> often multi family

• For complicated counties (e.g. Oakland), we have multiple X[x] logins because each department might need their own logins with different levels of permission

Authentication

• Validated through header file and sess files usually

“ccode” —> for people with multiple header files, we can do f”{header}ccode”

• look at CCCA as example

• most authentication is stored on the program page

Login credentials:

How new agency users get a login

• upon making an application they get given a login that is shared by the city as part of the application process.

• Each agency can have multiple logins but it’s not common

• Once they have a login and a program setup they can apply for additional funding from within that login and thereby have multiple programs under the same login for the same FY