With https://github.com/yuvipanda/jupyterhub-ssh, you can get 'real' ssh access to your JupyterHub instance, via your JupyterHub access token. This means anyone with a SUL login can then login to PAWS, get a token that'll let them *ssh* in. SFTP is also supported.

This appears to be outside of the scope of PAWS. The ephemeral nature of PAWS makes it good for testing, or running bots that need run manually, though it is poor for services that need continuous or scheduled running, much resource, or significant collaboration are not strong suits of PAWS. Indeed when these things are desired it is our normal process to direct people to Toolforge. As such having more clear lines between the two services (Toolforge and PAWS) is desirable.