Current Design Patterns
...
We don't have a great user-roles story.
Right now, we assume that having API access implies admin access.
Using a Django group: enterprise_enrollment_api_access
- Data API gets the JWT, calls the LMS to get the user details, looks up enterprise affiliation via an LMS API - can be chatty (though there is a cache).
- Keeps track of being "associated" with an enterprise.
Enterprise Roles
- Association with an enterprise (enterprise-customer-user)
- Role within the enterprise
- User
- Admin
- Financial Admin (future?)
- Theoretically, a user can be affiliated with multiple enterprises.
Masters requirements
- Flipped application process: managed by masters organization
- If based on enterprise, there may be a concept of having a "primary" enterprise.
- APIs
- Enrollments
- Cohort
- Grades
- Completion
- Student Records
Next Steps
- Nimisha Asthagiri (Deactivated) write current design thoughts on capturing system-wide roles in JWT tokens, and proposal for including enterprise association in JWTs.
- Douglas Hall (Deactivated), George Babey, Brittney Exline (Deactivated), Nimisha Asthagiri (Deactivated) Dive deeper into enterprise design (perhaps after/during step 1).
- Scott Dunn (Deactivated) share Masters use cases.
- Scott Dunn (Deactivated) answer the question: if we have the following organization types: enterprise-org and content-provider-org, where does masters fit in?