Added UserProfile to connect user to school(s).
Can now associate a user with a specific school(s), through admin site.
Creating a school automatically associates current user with that school.
Entire_system page responds appropriately to logged in status, and to proper school association.
Main view pages test for school association, and give proper response dependent on who is viewing.
Pathways show proper message depending on user's school association.
Profile page lists schools that you are associated with.
Editing school (subject_areas) requires association with school, redirects to no_edit_permission if not associated properly.
Edit permission checked in separate function, no_edit_permission links to school.
All edit pages, including hierarchy, pathways, and forking, check permissions appropriately.
Added subject_areas to UserProfile, and migrated.
User with subject_area-level privileges can edit public elements under the appropriate subject area.
Updated initial_data to include appropriate school and subject_area privileges for sample users.
User with subject_area-level privileges can see that school's entire system, and edit that subject_area's elements.
User with subject_area-level privileges can edit_order on that subject's elements.
Subject area editor can see visibility settings, but can't modify them.
Updated initial_data.
Added pathways to userprofile.
Guest editors can be given permission to edit selected pathways.
Users with subject_area-level edit permission can create pathways.