hi @regis! Thanks for the reply.
I saw the doc and would love to clarify following:
- Most of your users should probably not have access to all data from all courses. To restrict a given user to one or more courses or organizations, select the course IDs and/or organization IDS to which the user should have access and create a user with limited access to the datalake:
tutor local run cairn-clickhouse cairn createuser --course-id='course-v1:edX+DemoX+Demo_Course' --org-id='edX' YOURUSERNAME
so it means that any user logging to superset frontend he/she will see the same set of courses he has access to inside lms and we need to run above command only if we intend to restrict him/her for selected courses out of that set of allowed courses else command is totally unnecessary?
- Then, create the corresponding user on the frontend with the same command as above (but without the --admin option):
tutor local run cairn-superset cairn createuser YOURUSERNAME YOURUSERNAME@YOUREMAIL.COM
I saw this before and above question is based on this only. We set up our openedx with tutor and experimenting with enterprise-edx. My question is once the staff member is enterprise user and he has his own learners and course catalog, he should signin inside superset frontend with same login credentials what he uses for lms and see the metrics for courses and user he has access to. As above step feels like manually we have to provide login to them.
I would love to talk to you for any further possibilities regarding customization. Looking forward !!