We've been working on the tenant management branch here and have a few fixes ready for the todo items on the tenant management PR (adaptlearning/adapt_authoring#1637):
As part of the work to allow a tenant admin to change the owner of any course in their tenancy the tenant admin can see all courses in their tenant. This means that they can also delete courses in their tenant. However it seems to be the case that shared courses can only be deleted by the project owner - so a small change would be needed here for the following todo item to be checked off "Tenant admin: Able to remove any course in the tenancy".
We have also been working on the naming of a tenant database. Currently the "Tenant name" field is used as the database name. There is a scenario which can cause a database clash:
We have made a change so that the tenant id is used as the database name. This way it will always be unique and we don't have to worry about sanitising user input before it is used as the db name or scenarios like the above.
We would like to give these back to the tenant management branch but aren't sure on the best way to do it. Should we create a PR to the branch or just add the changes to it? They are just being tested and should be ready sometime tomorrow.
@dancgray I've noticed that when you first make a tenant its db doesn't appear in the db list. You have to create a user in that tenant and then that user needs to create something which would be stored in the tenant's db (eg. a course).
All users are stored in the master db, so just adding a user to a tenant won't be enough to 'create' the tenant db.
Hope that helps