Governance Role

The Governance decides which JupyterHub request will be approved and which will be denied. The criteria used to make this decision can be completely different depending on your institution.

It is also the responsibility of the governance to define the roles of the users, i.e. the governance also determines who is allowed to create JupyterHub requests at all.

Review JupyterHub Requests

You will receive a notification as soon as a JupyterHub Request needs review. This might be either when a new Request is created or when a change request is created.

For review, you need to have the role portal-admin. Login and open the Administration tab. Click on Review open Requests and select a JupyterHub Request to review. You may accept or decline this request with the corresponding buttons.

Manage JupyterHubs

As Governance you may at any time cancel JupyterHub Requests or even delete running JupyterHub deployments.

To do so, click on Search JupyterHubs in the Administration tab and select a JupyterHub. If the JupyterHub has not been started yet, you can cancel it. If it already has startet, you can mark it for degration or you can trigger a redeployment for example in cases of updates or a failed deployment.

Manage Users

This function is not yet implemented. The Governance should be able to create users and to manage users in terms of giving a user portal-leader or portal-admin roles. As long as this feature is not yet implemented, the governance need to assign these roles in authentik. Managing roles in authentik is not part of this document.

Misc Management

This function is not yet implementet. Access to this section will soon be deleted for the Governance, as the planned features are intended for the JHaaS Provider.