Skip to content

Instantly share code, notes, and snippets.

@JStans12
Last active February 7, 2017 00:42
Show Gist options
  • Save JStans12/2a583501360d8a9e3eafa2a9374812a9 to your computer and use it in GitHub Desktop.
Save JStans12/2a583501360d8a9e3eafa2a9374812a9 to your computer and use it in GitHub Desktop.

The lifecycle of user roles in Census

  • When an admin sends an invitation, they can select role from ["admin", "mentor", "student"].

  • If they select student, the new user will be given a role of either "enrolled", "active student" or "graduated" depending on the status of the cohort.

  • This makes 4 different roles that could be assigned to a new user.

  • There are 3 other roles which can be assigned later by an admin: ["exited", "removed", "graduated"]

Explanation of role permissions

  • Admin

    • Can crud all aspects of users.
    • Can manage applications
  • Active Student / Mentor / Graduated

    • Can read and update their own personal info.
    • Can join public groups.
    • Can read cohort information (view cohort pages).
    • Can manage applications
  • Enrolled

    • Can read and update their own personal info.
    • Can read cohort information (view cohort pages).
  • Exited / Removed

    • Can't do anything

Notes

Eventually, students will apply through Census. At this time, we don't have that functionality. We are assuming that all new Census users will be added by invitation once they have been accepted to Turing. We are ignoring the "applicant" role for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment