# Use Case: workshop

Real world use case:

> I am having a hackathon and want to add non-admin users and each user should only be allowed to run a single SLURM job at a time

### User and SLURM account creation helper script

Download this script and check that it is okay

{% file src="<https://2529223994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYO2RW7i8v8Hs8UzxSAdO%2Fuploads%2FekSMmvYsCv4xBhP8Xs1S%2Fcluster-make-users.sh?alt=media&token=2ac1b1f3-5746-4b0f-b8bb-f11eb854fc84>" %}

Modify the USERS map inside `clusters-make-users.sh` to add your users

Find the public IP of the jumphost in verda cloud console

Run it like this:

```bash
$ bash scripts/cluster-make-users.sh cluster.jumphost.public.ip
Login Success for idm_admin@auth.cluster.verda.internal
--- jsmitha1 ---
Creating kanidm user jsmitha1
Successfully created display_name="John Smith" username=jsmitha1
Setting posix attributes for jsmitha1
Successfully added ["jsmitha1"] to group "cluster_users"
Starting slurm sacctmgr changes & validation
SLURM add user jsmitha1
 Adding User(s)
  jsmitha1
 Settings
 Associations =
  C = wide-bird-cracks-fin-03 A = default_acct         U = jsmitha1 
Would you like to commit changes? (You have 30 seconds to decide)
(N/y): 

=== Summary ===
Cluster: wide-bird-cracks-fin-03
OK: jsmitha1
AccountingStorageEnforce: OK

```