From 1e4e80389a9479ac10d7b47015464ba418de0980 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Thu, 28 May 2026 16:31:13 +0000
Subject: [PATCH] docs: clarify porter auth logout server-side session
 revocation

---
 standard/cli/command-reference/porter-auth.mdx | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/standard/cli/command-reference/porter-auth.mdx b/standard/cli/command-reference/porter-auth.mdx
index 97f12f8..cca97ec 100644
--- a/standard/cli/command-reference/porter-auth.mdx
+++ b/standard/cli/command-reference/porter-auth.mdx
@@ -40,13 +40,22 @@ After logging in, Porter automatically sets your default project and cluster if
 
 ## `porter auth logout`
 
-Log out from Porter and clear your local credentials.
+Log out from Porter. This revokes your current session on the Porter API and clears your local credentials, so any cached access or refresh tokens stored on disk can no longer be used.
 
 **Usage:**
 ```bash
 porter auth logout
 ```
 
+**Example:**
+```bash
+porter auth logout
+```
+
 <Tip>
 After logging out, you'll need to run `porter auth login` again before using other commands.
 </Tip>
+
+<Info>
+Use `porter auth logout` on shared or untrusted machines before stepping away. Simply deleting the local config file leaves your session valid on the server — only `porter auth logout` revokes it.
+</Info>