rubyforgood / growhaus_sign_in Goto Github PK

Requested by GrowHaus: "I don't think we're too worried about non-staff maliciously using the admin feature. GH [GrowHaus, not GitHub] staff will be present in some capacity most of the time when volunteers/interns are logging in and out. Having an easy way to return to admin view would be ideal."

IIRC there is some enforcement code (which we can basically remove), otherwise this is just adding a link.

The questionnaire page (user new) will gather the following info from the user:

• Name (split this up)
• Address (split this up)
• Email Address
• drop down with some title i can't think of
  • Volunteer
  • Intern
  • Visitor
• Display a scrollable waiver for them to read
• Have an I Agree checkbox
• Accept their e-signature (@rlwinter to provide details on requirements for this)
• Submit button

The submit button will take the user to either:

• The next page of the questionnaire needed based on Volunteer vs intern vs visitor
• Choose action page

doesn't look right with the extra column sort icons

Requested by GrowHaus. The proposed method is to embed a google form rather use a rails form, so this would be a big change.

This page lets you do things like:

• link to generate reports
• link to switch to welcome mode
• see staff users who have logged in before (nice to have)

This could be complicated, but one idea is to:

• In dev/test mode, allow user to log in with fixture username and password
• In prod, Google app authentication against the @growhaus.com domain.

• mark required fields as required
• mark conditionally required fields as required with their conditions
• properly report the reason why a field is required (e.g., role requires it)
• repeat the requirement reason in the error message
• explain the /s/ signature convention and how it represents a legally binding signature
• explain the /s/ signature convention again in the error message

When creating a new activity session, close any existing ones

Part of fixing this issue is providing instructions to the team members on how to define text in the views, so it is dynamic.

The choose action page will be accessible for a specific user.
As a user, I am able to either choose an activity to start tracking time against or choose to check out, if I am currently logging time against an activity.
Choosing an activity starts logging time for me against that activity.
Checking out stops logging time for me against my current activity.

Once you are in welcome mode, you shouldn't be able to get back to the staff or report generation pages.

Running 'rake db:seed' should be idempotent

Right now it's just a plain bullet list item

The app should be blocked from anyone using it, unless they are authenticated. (No extra authorization required).

All pages should redirect to The Login Page.

Requested by GrowHaus.

• Set production DB to postgres
• Use environment variables for all production keys, tokens, and credentials
  • db username
  • db password
  • MailChimp api key
  • etc
• Enable capistrano?

Right now pulling model names for activity but they are all in english right now

New email addresses submitted via the new user sign up page should be added to the growhaus mailing list.

The welcome page should contain the following parts:

• Welcome message
• New User button and description
  • This will link to the sign up questionnaire page
• Returning user and description
  • This will link to the users index page

In production, only @growhaus emails should get access to the app.

To match the look and feel with the company website, since this app is customer facing. The site uses Google Font Lato

Need a way for user to cancel a workflow

• set end time of all activity_sessions
• remove all staff sessions

May need Growhaus to provide a centered image. This image is from the main Growhaus site.

This page will list out every user in a datatables searchable table.
Each user can be clicked on.
Clicking on a specific user moves you to the choose action page.

Currently there are none in the seed data.