> ## Documentation Index
> Fetch the complete documentation index at: https://docs.celestia.rest/llms.txt
> Use this file to discover all available pages before exploring further.

# Antinuke Administrators

> Designate trusted users to manage antinuke protections without server ownership

## Overview

The Antinuke system uses a three-tier permission hierarchy to give server owners fine-grained control over who can manage security settings. Extra Owners act as co-owners for antinuke purposes, while Antinuke Admins have limited access to enable protections only.

<Info>
  Antinuke Admins can enable protections but cannot disable them or change punishments. For full access, use the Extra Owner system instead.
</Info>

***

## Access Control

| Action                  | Server Owner | Extra Owner | Antinuke Admin |
| ----------------------- | ------------ | ----------- | -------------- |
| Manage extra owners     | ✅            | ❌           | ❌              |
| Manage antinuke admins  | ✅            | ✅           | ❌              |
| Enable protections      | ✅            | ✅           | ✅              |
| Disable protections     | ✅            | ✅           | ❌              |
| Change punishments      | ✅            | ✅           | ❌              |
| Configure Verdict Mode  | ✅            | ✅           | ❌              |
| Exempt from punishments | ✅            | ✅           | ✅              |
| Can be removed          | ❌ Never      | ✅           | ✅              |

***

## Extra Owners

Extra Owners have elevated antinuke access equivalent to the server owner. They can manage antinuke admins, enable and disable protections, change punishments, and configure Verdict Mode.

<Warning>
  Extra Owners have near-full antinuke control. Only assign this role to highly trusted users.
</Warning>

### Commands

<AccordionGroup>
  <Accordion title="extraowner add" icon="user-plus">
    Add a user as an extra owner to grant them elevated antinuke access.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~extraowner <@user>
      ```

      ```bash Example theme={null}
      ~extraowner @TrustedCoOwner
      ~eo @SecurityLead
      ~xowner @HeadAdmin
      ```
    </CodeGroup>

    **Aliases:** `eo`, `xowner`\
    **Permissions:** Server Owner only\
    **Limit:** 3 extra owners per server
  </Accordion>

  <Accordion title="extraowner remove" icon="user-minus">
    Remove a user from the extra owner list.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~extraowner remove <@user>
      ```

      ```bash Example theme={null}
      ~extraowner remove @FormerCoOwner
      ~eo remove @ExStaff
      ```
    </CodeGroup>

    **Aliases:** `eo remove`, `xowner remove`\
    **Permissions:** Server Owner only
  </Accordion>

  <Accordion title="extraowner list" icon="list">
    View all extra owners for your server.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~extraowner list
      ```

      ```bash Example theme={null}
      ~extraowner list
      ~eo list
      ```
    </CodeGroup>

    **Aliases:** `eo list`, `xowner list`\
    **Permissions:** Server Owner only
  </Accordion>
</AccordionGroup>

***

## Antinuke Admins

Antinuke Admins are trusted users who can enable antinuke protections. They cannot disable protections, change punishments, or access Verdict Mode configuration.

<Note>
  If you need a user to have full antinuke control, use Extra Owner instead of Antinuke Admin.
</Note>

### Commands

<AccordionGroup>
  <Accordion title="antinukeadmin add" icon="user-plus">
    Add a user as an antinuke administrator.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~antinukeadmin <@user>
      ```

      ```bash Example theme={null}
      ~antinukeadmin @TrustedStaff
      ~ana @SecurityManager
      ~antiadmin @HeadModerator
      ```
    </CodeGroup>

    **Aliases:** `ana`, `antiadmin`\
    **Permissions:** Server Owner or Extra Owner\
    **Limit:** 3 admins per server

    <Tip>
      Antinuke admins can only enable protections. If you want them to also disable or configure punishments, add them as an Extra Owner instead.
    </Tip>
  </Accordion>

  <Accordion title="antinukeadmin remove" icon="user-minus">
    Remove a user from the antinuke administrator list.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~antinukeadmin remove <@user>
      ```

      ```bash Example theme={null}
      ~antinukeadmin remove @FormerAdmin
      ~ana remove @ExStaff
      ```
    </CodeGroup>

    **Aliases:** `ana remove`, `antiadmin remove`\
    **Permissions:** Server Owner or Extra Owner
  </Accordion>

  <Accordion title="antinukeadmin list" icon="list">
    View all antinuke administrators for your server.

    <CodeGroup>
      ```bash Syntax theme={null}
      ~antinukeadmin list
      ~antinukeadmin
      ```

      ```bash Example theme={null}
      ~antinukeadmin list
      ~ana list
      ~antiadmin
      ```
    </CodeGroup>

    **Aliases:** `ana list`, `antiadmin list`\
    **Permissions:** Server Owner or Extra Owner
  </Accordion>
</AccordionGroup>

***

## Privilege Summary

<Tabs>
  <Tab title="Extra Owner">
    Extra owners can:

    * Enable and disable all antinuke protections
    * Change punishment types for any protection
    * Manage antinuke admins (add and remove)
    * Configure and toggle Verdict Mode
    * Set and modify the log channel
    * Access and use all antinuke commands

    Extra owners cannot:

    * Add or remove other extra owners
    * Override the server owner
  </Tab>

  <Tab title="Antinuke Admin">
    Antinuke admins can:

    * Enable antinuke protections
    * View protection status and configuration
    * Access antinuke commands that don't require full access

    Antinuke admins cannot:

    * Disable protections
    * Change punishments
    * Manage other antinuke admins or extra owners
    * Configure Verdict Mode
  </Tab>

  <Tab title="Limitations">
    Neither extra owners nor antinuke admins can:

    * Manage extra owners (server owner only)
    * Override the server owner's decisions
    * Modify server ownership
    * Bypass antinuke protections themselves
  </Tab>
</Tabs>

***

## Slot Limits

<Warning>
  **Maximum Limits**

  * Extra Owners: **3 per server**
  * Antinuke Admins: **3 per server**

  The server owner and bot developers do not count toward either limit.
</Warning>

***

## How It Works

<Steps>
  <Step title="Server Owner Level">
    The server owner has supreme authority over the entire antinuke system. They are the only one who can manage extra owners and cannot be removed from antinuke access.
  </Step>

  <Step title="Extra Owner Level">
    Extra owners have near-full antinuke access. They can manage antinuke admins and configure all protection settings except managing extra owners themselves.
  </Step>

  <Step title="Antinuke Admin Level">
    Antinuke admins have restricted access. They can enable protections to help respond to threats, but cannot alter the overall configuration or disable existing protections.
  </Step>

  <Step title="Regular User Level">
    Standard members cannot access any antinuke commands and are subject to all active protections. They can be whitelisted separately to exempt them from punishments.
  </Step>
</Steps>

***

## Best Practices

<Steps>
  <Step title="Use Extra Owners for Trusted Co-Admins">
    Assign extra owners to users who need full antinuke control, such as co-owners or head admins.

    ```bash theme={null}
    ~extraowner @TrustedCoOwner
    ```

    <Warning>
      Extra owners can disable protections and change punishments. Only assign this to users you fully trust.
    </Warning>
  </Step>

  <Step title="Use Antinuke Admins for Limited Staff Access">
    Assign antinuke admins to moderators who should be able to activate protections during an attack but shouldn't be able to alter the configuration.

    ```bash theme={null}
    ~antinukeadmin @SecurityModerator
    ```
  </Step>

  <Step title="Keep Numbers Minimal">
    Use as few slots as necessary. Extra owners especially should be kept to 1-2 users maximum.

    ```bash theme={null}
    ~extraowner list
    ~antinukeadmin list
    ```
  </Step>

  <Step title="Regular Audits">
    Review both lists periodically, especially after staff changes.

    ```bash theme={null}
    ~extraowner list
    ~antinukeadmin list
    ```
  </Step>

  <Step title="Remove Access Immediately When Needed">
    Promptly remove users who are no longer trusted or active.

    ```bash theme={null}
    ~extraowner remove @FormerStaff
    ~antinukeadmin remove @InactiveUser
    ```
  </Step>
</Steps>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Cannot add — maximum reached" icon="octagon-exclamation">
    **Problem:** You've hit the 3-user limit for extra owners or antinuke admins.

    **Solution:**

    1. View current list: `~extraowner list` or `~antinukeadmin list`
    2. Remove an inactive user: `~extraowner remove @user` or `~antinukeadmin remove @user`
    3. Add the new user
  </Accordion>

  <Accordion title="User already added" icon="circle-info">
    **Problem:** Trying to add someone who's already in the list.

    **Solution:** Check the current list with `~extraowner list` or `~antinukeadmin list`.
  </Accordion>

  <Accordion title="Cannot add the server owner" icon="crown">
    **Problem:** Attempting to add the server owner.

    **Explanation:** The server owner automatically has full access and doesn't need to be added to either list.
  </Accordion>

  <Accordion title="Cannot add bots" icon="robot">
    **Problem:** Trying to add a bot as an extra owner or antinuke admin.

    **Explanation:** Only human users can be added. Bots should be managed through the whitelist system instead.
  </Accordion>

  <Accordion title="Permission denied on antinukeadmin command" icon="ban">
    **Problem:** Cannot manage antinuke admins.

    **Explanation:** Only the server owner and extra owners can manage antinuke admins. Regular antinuke admins cannot add or remove other admins.
  </Accordion>

  <Accordion title="Permission denied on extraowner command" icon="lock">
    **Problem:** Cannot manage extra owners.

    **Explanation:** Only the server owner can manage extra owners. Extra owners themselves cannot add or remove other extra owners.
  </Accordion>

  <Accordion title="Antinuke admin cannot disable protection" icon="shield-xmark">
    **Problem:** Antinuke admin tries to disable a protection and gets denied.

    **Explanation:** This is by design. Antinuke admins can only enable protections. To disable protections, the user needs to be an extra owner or server owner.
  </Accordion>
</AccordionGroup>

***

## Security Recommendations

<CardGroup cols={2}>
  <Card title="Trust Verification" icon="handshake">
    Thoroughly vet users before granting extra owner access. They can disable your entire antinuke configuration.
  </Card>

  <Card title="Minimal Access" icon="lock">
    Use antinuke admin instead of extra owner whenever full access isn't strictly necessary.
  </Card>

  <Card title="Regular Reviews" icon="clipboard-check">
    Audit both lists monthly or after any staff changes to ensure only active, trusted members have access.
  </Card>

  <Card title="Immediate Revocation" icon="bolt">
    Remove access immediately if you notice suspicious behavior or if an account is compromised.
  </Card>
</CardGroup>

***

## Related Features

<CardGroup cols={2}>
  <Card title="Antinuke System" icon="shield-halved" href="/antinuke">
    Explore all antinuke protection modules and the main control panel
  </Card>

  <Card title="Whitelist System" icon="shield-check" href="/whitelist">
    Exempt users from antinuke punishments without giving them configuration access
  </Card>

  <Card title="Verdict Mode" icon="gavel" href="/verdict">
    Threshold-based antinuke system accessible to server owners and extra owners
  </Card>

  <Card title="Antinuke Logs" icon="scroll" href="/antinuke-logs">
    Configure a dedicated channel to monitor all antinuke events
  </Card>
</CardGroup>