diff --git a/assets/doc_img/token.png b/assets/doc_img/token.png
new file mode 100644
index 0000000..f70b72b
Binary files /dev/null and b/assets/doc_img/token.png differ
diff --git a/user-guide/compute-env.md b/user-guide/compute-env.md
index cb93273..a286c6e 100755
--- a/user-guide/compute-env.md
+++ b/user-guide/compute-env.md
@@ -53,7 +53,12 @@ The following steps need to be completed in order unless they have been complete
You don’t need an access token if you intend to create SSH key credentials, but you will need it for the Tower Agent credentials.
- - The user can create an access token as described here.
+ - Navigate to the
User Tokens from the user menu on the top-right corner:
+
+
+
+
+ - Click
Add Token and give the token a name.
- Keep it safe, create a new one if you lose it and delete lost tokens.
- Use descriptive names.
- Don’t share your token with others.
@@ -88,7 +93,7 @@ The following steps need to be completed in order unless they have been complete
- Keep the Agent interface open.
- Log in to infrastructure (the HPC).
- - In theory, you can run the Agent from anywhere on the HPC. See our [best practices](/user-guide/hpc-recommendations) for some recommendations.
+ - In theory, you can run the Agent from anywhere on the HPC. See our best practices for some recommendations.
- Copy the usage script from the Agent interface to any text editor and edit the access token to provide your own token created above and provide the path to the work directory for the Agent.
- The work directory for the Agent (provided as a parameter in the command) must exist before running the Agent.
- Run the edited script relevant to your infrastructure (PBS or SLURM) bash.