access

Discord channel access control can be managed locally by reading and validating a JSON state file to apply argument-dispatched mutations for approvals, allowlists, and DM policies. This safely persists changes to disk without direct API calls.

Pending Discord pairing requests are approved or denied by updating the local authorization state in your access configuration file. This validates the pending code, applies the mutation, expires outdated codes, and confirms the approved sender.

Switching the DM policy to allowlist mode involves updating the dmPolicy setting in your local JSON state file. Once set, the channel restricts direct messages exclusively to the sender IDs listed in the allowlist.

Yes, you can add or remove specific Discord sender IDs by applying argument-dispatched mutations to the local access configuration. The process automatically deduplicates allowFrom entries to maintain a clean list of authorized users.

Managing access through local JSON state files requires safely reading and validating the configuration before applying mutations. It relies entirely on terminal requests for updates and does not directly call Discord APIs to enforce the policy changes.