Access and server observations

Prepare for onboarding#

1. Identify the Discord server and the owner or administrator who will authorize access.
2. Contact support for the approved installation and administration entry point.
3. Sign in through the supplied Discord authorization flow and verify the selected server.
4. Review the requested read access and the consent scope before running an observation.

Read an observation#

Check which server was observed, the observation time, and whether the result is current or incomplete. A report describes the state the service could observe with its permissions at that time. A missing or failed check must not be treated as a clean bill of health.

What a scan authorizes#

Read access allows observation within its scope. It does not authorize permission changes, role changes, deletion, or repairs. An observation may be used to prepare a proposed plan, but applying it is a separate governed operation where enabled.

If changes are suggested#

Read plans and approvals before accepting a proposed change. If the service shows the operation is unavailable, stop at the report and ask support about access; there is no public slash-command workaround documented here.