DOCS-4936: Correct user_permissions guidance for cloud-managed machines

[Jeremy Rose (jeremyrose-viam)]

The "Use Viam from an agent" page said a machine restricts an API key or user through user_permissions in the machine's JSON config, and told agents the machine owner could adjust it through the Viam app's JSON config editor. On a machine managed in the Viam app, that doesn't work: saving a config that contains auth.user_permissions is rejected with "auth.user_permissions is generated from access_policy at render and cannot be set in config; it appears in rendered configs, so remove it and edit access_policy instead". An agent following the old text would look for, or try to write, a field it can't set there.

What the page says now:

• viam-server enforces restrictions from a user_permissions list in the auth section of the config it runs.
• On a standalone viam-server with a local config file, that list is in the file.
• On a machine managed in the Viam app, the agent doesn't write the list, because the app rejects it.
• The existing guidance to report permission errors and the entries it finds to the human operator is kept. The page no longer says the operator adjusts it through the app's JSON editor.

Refs DOCS-4936.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for viam-docs ready!

Name	Link
🔨 Latest commit	d460f16
🔍 Latest deploy log	https://app.netlify.com/projects/viam-docs/deploys/6ad182cd4bb335a2ab3989cd
😎 Deploy Preview	https://deploy-preview-5428--viam-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 37 (🟢 up 2 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.