> ## 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.

# Extra Owners

> Grant trusted users elevated antinuke control equivalent to the server owner

## Overview

Extra Owners are trusted users who have near-full antinuke access equivalent to the server owner. They can manage antinuke admins, enable and disable all protections, change punishments, and configure Verdict Mode — everything except managing other extra owners.

<Warning>
  Extra Owners have significant control over your server's security configuration. Only assign this role to users you completely trust.
</Warning>

***

## Access Control

Only the server owner can manage extra owners.

<Note>
  Extra owners cannot add or remove other extra owners. This privilege is reserved exclusively for the server owner.
</Note>

***

## 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

    <Tip>
      Use this for co-owners or head admins who need full antinuke control. For staff who only need to enable protections, use `~antinukeadmin` instead.
    </Tip>
  </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
      ~xowner remove @user
      ```
    </CodeGroup>

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

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

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

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

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

***

## What Extra Owners Can Do

<Tabs>
  <Tab title="Protection Management">
    Full control over all antinuke protection modules:

    * Enable and disable any protection
    * Change punishment types (ban, kick, strip)
    * Use the global punishment selector
    * Enable and disable all protections at once
    * Configure individual protections via dedicated commands
  </Tab>

  <Tab title="Admin Management">
    Manage the antinuke admin tier:

    * Add antinuke admins
    * Remove antinuke admins
    * View the antinuke admin list
  </Tab>

  <Tab title="Verdict Mode">
    Full Verdict Mode configuration:

    * Enable and disable Verdict Mode
    * Toggle individual verdict protections
    * Set custom thresholds and time windows
    * Reset thresholds to default
    * View verdict configuration and status
  </Tab>

  <Tab title="Limitations">
    What extra owners cannot do:

    * Add or remove other extra owners
    * Override the server owner
    * Bypass antinuke protections themselves
  </Tab>
</Tabs>

***

## Slot Limit

<Warning>
  **Maximum of 3 Extra Owners per server.**

  The server owner and bot developers do not count toward this limit. If you've reached the limit, you must remove an existing extra owner before adding a new one.
</Warning>

***

## Extra Owner vs Antinuke Admin

<CardGroup cols={2}>
  <Card title="Extra Owner" icon="crown">
    * Enable and **disable** protections
    * **Change** punishments
    * Manage antinuke admins
    * Configure Verdict Mode
    * Near-full antinuke access
    * Limit: 3 per server
  </Card>

  <Card title="Antinuke Admin" icon="user-shield">
    * Enable protections only
    * Cannot disable or change punishments
    * Cannot manage other admins
    * No Verdict Mode access
    * Limited antinuke access
    * Limit: 3 per server
  </Card>
</CardGroup>

<Tip>
  Use Extra Owner for co-owners and head admins. Use Antinuke Admin for moderators who should be able to activate protections but not alter the overall configuration.
</Tip>

***

## Setup Guide

<Steps>
  <Step title="Identify Trusted Users">
    Decide which users need full antinuke access. These should be co-owners, head admins, or users you trust as much as yourself with your server's security.
  </Step>

  <Step title="Add Extra Owners">
    Add each trusted user as an extra owner.

    ```bash theme={null}
    ~extraowner @CoOwner
    ~extraowner @HeadAdmin
    ```
  </Step>

  <Step title="Verify the List">
    Confirm the correct users were added.

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

  <Step title="Inform Extra Owners">
    Let your extra owners know what they have access to and what your expectations are for managing the antinuke system.
  </Step>
</Steps>

***

## Best Practices

<Steps>
  <Step title="Keep Numbers Low">
    1-2 extra owners is usually enough. The fewer people with full access, the lower your attack surface.

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

  <Step title="Audit Regularly">
    Review the extra owner list after any staff changes to make sure only active, trusted users have access.

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

  <Step title="Remove Access Promptly">
    Remove extra owner access immediately if a user leaves, becomes inactive, or loses your trust.

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

  <Step title="Use Antinuke Admin for Limited Access">
    If a user only needs to be able to enable protections during an incident, use `~antinukeadmin` instead of `~extraowner`.

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

***

## Common Use Cases

<AccordionGroup>
  <Accordion title="Co-Owner Setup" icon="handshake">
    Grant a trusted co-owner full antinuke access.

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

    They can now manage all antinuke settings and admins just like you.
  </Accordion>

  <Accordion title="Head Admin Access" icon="shield-halved">
    Give your head admin the ability to fully configure antinuke without needing to contact you.

    ```bash theme={null}
    ~extraowner @HeadAdmin
    ```
  </Accordion>

  <Accordion title="Rotating Staff" icon="rotate">
    When a trusted staff member is promoted or steps down, update the list accordingly.

    ```bash theme={null}
    # Remove outgoing extra owner
    ~extraowner remove @SteppingDown

    # Add incoming extra owner
    ~extraowner @NewCoOwner
    ```
  </Accordion>

  <Accordion title="Emergency Removal" icon="user-xmark">
    Immediately revoke access if an extra owner's account is compromised or they abuse their privileges.

    ```bash theme={null}
    ~extraowner remove @CompromisedAccount
    ```
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

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

    **Solution:**

    1. View current extra owners: `~extraowner list`
    2. Remove one: `~extraowner remove @user`
    3. Add the new user: `~extraowner @newuser`
  </Accordion>

  <Accordion title="User already an extra owner" icon="circle-info">
    **Problem:** Trying to add someone who's already an extra owner.

    **Solution:** Check the list with `~extraowner list` to see who's already been added.
  </Accordion>

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

    **Explanation:** The server owner already has full access by default and doesn't need to be added.
  </Accordion>

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

    **Explanation:** Only human users can be extra owners. Use the whitelist system to exempt bots from punishments.
  </Accordion>

  <Accordion title="Permission denied" icon="ban">
    **Problem:** Cannot run the extraowner command.

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

  <Accordion title="User not found" icon="magnifying-glass">
    **Problem:** Invalid user mention or ID.

    **Solution:**

    * Mention the user directly: `~extraowner @username`
    * Or use their user ID: `~extraowner 123456789012345678`
    * Verify the user is in the server
  </Accordion>
</AccordionGroup>

***

## Security Considerations

<Warning>
  **Extra owners can:**

  * Disable all antinuke protections
  * Change punishments to none, removing all enforcement
  * Add and remove antinuke admins
  * Fully reconfigure Verdict Mode

  A compromised or malicious extra owner can effectively disarm your entire antinuke system. Choose carefully and revoke access immediately if anything seems suspicious.
</Warning>

***

## Related Features

<CardGroup cols={2}>
  <Card title="Antinuke Administrators" icon="user-shield" href="/antinuke-administrators">
    Set up limited-access admins who can only enable protections
  </Card>

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

  <Card title="Verdict Mode" icon="gavel" href="/verdict">
    Threshold-based antinuke system that extra owners can fully configure
  </Card>

  <Card title="Whitelist System" icon="shield-check" href="/whitelist">
    Exempt trusted users and bots from antinuke punishments
  </Card>
</CardGroup>