gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-22 11:13:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add missing user permissions step for PBS API token setup

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
courtmanr@gmail.com
2025-05-29 21:09:41 +01:00
parent bfda5974bc
commit b72ef97d43
1 changed files with 4 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -7
View File
@@ -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`.
</details>