> For the complete documentation index, see [llms.txt](https://wyne.gitbook.io/wyne-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wyne.gitbook.io/wyne-docs/connectionsource/commands-and-permissions.md).

# Commands and permissions

One command, /connection reload, its confirmation step, and the two permissions that guard it.

## Commands

| Command                      | Permission          | What it does                                                                                                              |
| ---------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `/connection reload`         | `connection.reload` | Reloads the config and rebuilds the pool—unless a pool is already active, in which case it warns and asks you to confirm. |
| `/connection reload confirm` | `connection.reload` | Reloads unconditionally, active pool or not.                                                                              |

A reload re-reads `config.yml`, re-applies `logLevel`, registers the configured JDBC driver if that driver isn't registered yet, closes the current pool, and opens a new one from the new settings.

## Why the confirmation exists

Run `/connection reload` while the pool is live and you get this instead of a reload:

```
Connection source is already active.
Are you sure you want to reload the connection source? It may cause data loss in dependant plugins.
To confirm, type /connection reload confirm
```

The warning is about the other plugins on the server. A reload closes the pool they're sharing, and any plugin holding a reference to it—or to the ORMLite `ConnectionSource` it exposes—is left with a closed one. Writes in flight at that moment can fail. The safe sequence is to stop what's writing first, or to restart the server instead.

Consumer plugins can avoid the problem by fetching the pool from the provider rather than caching it. See [Rules for sharing a pool](/wyne-docs/connectionsource/using-it-from-your-plugin.md#rules-for-sharing-a-pool).

## Permissions

| Permission          | Default  | Grants                                                              |
| ------------------- | -------- | ------------------------------------------------------------------- |
| `connection.reload` | Operator | Both forms of `/connection reload`.                                 |
| `connection.*`      | Operator | Every ConnectionSource permission, which means `connection.reload`. |

## When CommandAPI is missing

The command is registered through [CommandAPI](https://commandapi.jorel.dev), a soft dependency. If it isn't installed, ConnectionSource logs `CommandAPI not found, commands are not registered` at startup and runs without the command—the pool works as usual, and config changes take effect on the next server restart.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wyne.gitbook.io/wyne-docs/connectionsource/commands-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.