diff --git a/README.md b/README.md
index a9087db96..73b48eb78 100644
--- a/README.md
+++ b/README.md
@@ -56,7 +56,7 @@ LiveKit is published to Docker Hub under livekit/livekit-server
 ### Creating API keys
 
 LiveKit utilizes JWT based access tokens for authentication to all of its APIs.
-Because of this, the server needs a list of valid API keys and secrets to validate the provided tokens. For more, see [Authentication](docs/authentication.md).
+Because of this, the server needs a list of valid API keys and secrets to validate the provided tokens. For more, see [Access Tokens](https://docs.livekit.io/guides/access-tokens).
 
 Generate API key/secret pairs with:
 
diff --git a/docs/authentication.md b/docs/authentication.md
deleted file mode 100644
index 53fb3ba26..000000000
--- a/docs/authentication.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Authentication
-
-LiveKit uses access tokens (JWT) to authenticate clients. A pair of API key and secret key is used to authenticate each API holder.
-
-An access token encapsulate a few pieces of information:
-
-- Grants: what permissions does this token have
-- Issuer: which api key issued the token
-- Expiration: how long should it be valid for
-- Identity: the participant's identity (when joining a room)
-
-Access tokens can be created with `livekit-cli`, or any of the livekit server SDKs