diff --git a/docs/auth_guide.md b/docs/auth_guide.md
index 838fd6cdf..ec234928c 100644
--- a/docs/auth_guide.md
+++ b/docs/auth_guide.md
@@ -4,18 +4,31 @@
 
 By default, the Toolkit does not enforce any authentication strategies, but they can be enabled from `src/backend/config/auth.py`.
 
-The list of implemented authentication strategies exist in `src/backend/services/auth`. Currently, there exists:
-- BasicAuthentication (for email/password auth): no setup required.
-- GoogleOAuth (Currently not ready - still requiring frontend integration and E2E testing, targeting mid-June): requires setting up [Google OAuth 2.0](https://support.google.com/cloud/answer/6158849?hl=en). You will need to retrieve a client ID and client secret and set them as environment variables.
+This is the current list of implemented Auth strategies:
 
-To enable one or more of these strategies, simply add them to the `ENABLED_AUTH_STRATEGIES` list in the configurations.
+- BasicAuthentication (for email/password auth): no setup required.
+- GoogleOAuth: requires setting up [Google OAuth 2.0](https://support.google.com/cloud/answer/6158849?hl=en). To enable this strategy, you will need to configure your Google OAuth app and retrieve `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` values.
+- OpenIDConnect: To enable this strategy, you will need to configure your SSO app and retrieve `OIDC_CLIENT_ID`, `OIDC_CLIENT_SECRET`, and `OIDC_WELL_KNOWN_ENDPOINT` values. Note that this should work with any OAuth app that follows OpenID Connect conventions, the strategy assumes that the well-known endpoint will return the required endpoints. See `oidc.py` for implementation details.
 
-After enabling one or more strategies, you must create a secret key to be used to encrypt the JWT tokens generated by the backend and store it in the `JWT_SECRET_KEY` environment variable.
+To enable one or more of these strategies, add them to the `ENABLED_AUTH_STRATEGIES` list in the `backend/config/auth.py` file, then add any required environment variables in your `.env` file, and generate a secret key to be used as the `AUTH_SECRET_KEY` environment variable. This is used to encode and decode your access tokens.
 
-For testing use-cases, you can enter any string value.
-For production use-cases, We recommend running the following in a local CLI to generate a random key:
+For the `AUTH_SECRET_KEY`, if you want to test auth functionality you can use any string value.
+For production use-cases, it is recommended to run the following python commands in a local CLI to generate a random key:
 
 ```
 import secrets
 print(secrets.token_hex(32))
 ```
+
+## Configuring your OAuth app's Redirect URI
+
+When configuring your OAuth apps, make sure to whitelist the Redirect URI to the frontend endpoint, it should look like 
+`<FRONTEND_HOST>/auth/<STRATEGY_NAME>`. For example, your Redirect URI will be `http://localhost:4000/auth/google` if you're running the GoogleOAuth class locally.
+
+## Implementing new Auth strategies
+
+To implement a new strategy, refer to the `backend/services/auth/strategies` folder. Auth strategies will need to inherit from one of two base classes, `BaseAuthenticationStrategy` or `BaseOAuthStrategy`.
+
+If your strategy requires environment variables, create a new `<AUTH_METHOD>Settings` class that inherits from `Settings`. The values you set in your Settings class will automatically be retrieved from the `.env` file.
+
+OAuth strategies should implement the `authorize` method to verify an authorization code and return an access token.