The original idea was allow non-admin users (teachers and students) to user Dashboard as main interface, while administrators (the project’s maintainers) can use SSH and non-protected URLs via VPN - like RabbitMQ Web interface. After some readings about admin role (and its privileges, literally, crossing over tenants), I decided to create a “superadmin” role: it denies admin users (including the admin itself and all services users such as glance or cinder) to login into Dashboard. Maybe RBAC is a better solution - I’ll study it in the next days…