From b72ef97d43856099989f7ea8b7e5ee5201253011 Mon Sep 17 00:00:00 2001 From: "courtmanr@gmail.com" Date: Thu, 29 May 2025 21:09:41 +0100 Subject: [PATCH] docs: add missing user permissions step for PBS API token setup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The PBS documentation was missing the step to add user permissions, only mentioning token permissions. This matches the PVE documentation which correctly shows both user AND token permissions are needed. Fixes #89 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- README.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index f5d93a713..1f02910fa 100644 --- a/README.md +++ b/README.md @@ -424,14 +424,11 @@ If monitoring PBS, create a token within the PBS interface. * Enter `Token Name` (e.g., "pulse"). * Leave `Privilege Separation` checked. Click `Add`. * **Important:** Copy the `Secret` value immediately. -4. **Assign permissions:** +4. **Assign permissions (to User and Token):** * Go to `Configuration` → `Access Control` → `Permissions`. - * Click `Add` → `API Token Permission`. - * Path: `/` (root level). - * API Token: Select the token (e.g., "pulse-monitor@pbs!pulse"). - * Role: `Audit`. - * Check `Propagate`. Click `Add`. - * *Note: The `Audit` role at root path (`/`) is needed for read-only access.* + * **Add User Permission:** Click `Add` → `User Permission`. Path: `/`, User: `pulse-monitor@pbs`, Role: `Audit`, check `Propagate`. Click `Add`. + * **Add API Token Permission:** Click `Add` → `API Token Permission`. Path: `/`, API Token: `pulse-monitor@pbs!pulse`, Role: `Audit`, check `Propagate`. Click `Add`. + * *Note: The `Audit` role at root path (`/`) with `Propagate` is crucial for both user and token.* 5. **Update `.env`:** Set `PBS_TOKEN_ID` (e.g., `pulse-monitor@pbs!pulse`) and `PBS_TOKEN_SECRET`.