Reviewing Plans
A short request can imply several concrete operations. Review the proposed changes, not only the request summary.
Review checklist
Section titled “Review checklist”| Check | Why it matters |
|---|---|
| Selected server | Prevent changes to another community |
| Current plan revision | Approval must refer to the exact current draft |
| Names and IDs | Similar names may identify different resources |
| Parent category | Channel inheritance can change effective access |
| Roles and overwrites | Private access depends on permissions, not names |
| Operation order | Later operations may depend on earlier results |
| Risks and deletions | Some effects cannot be automatically reversed |
Revise or cancel
Section titled “Revise or cancel”If an operation is unclear, revise the request and inspect the new draft. Do not approve merely to discover what the plan does. Fresh role/server context can invalidate old assumptions.
Approval is not a blanket grant
Section titled “Approval is not a blanket grant”The apply workflow checks current authority and exact plan state again. Losing access or changing a revision can require another review. Nothing in these docs or the local homepage demo counts as approval for a real server.