LindaKivine
commented
2 years ago These points about superorg shouldn't be public facing
- Manual assignment of a child org to a super org. (Clients need to contact us and we do this for them)
- An endpoint to return the list of child orgs, and their data.
- Frontend connection to this endpoint, being able to see superorg details in console.
- Billing of child orgs, counting as superorg usage. This means our customers dont need to buy separate plans for each child org, and can handle their own billing.
- Logs and summary of child org usage. (This is not connected to frontend at the moment, as we are lacking the design and fe engineers)
- Child orgs not being able to see super org details, usage or credits.
- Blocking routes per child org, blocking their access to some resources.
I added a few things here. And fixed the setup