Flynn Forge install

Install Flynn with a clear plan.

Flynn joins your server as an operations platform. Setup remains owner-reviewed, permission-aware, and routed through approved Change Plans before Discord changes are applied.

Install Flynn Back to home

What happens next

A professional installation path

User clicks Install Flynn.
Discord opens the server authorization flow.
The server owner reviews requested permissions.
Discord returns authorization to the Flynn API.
The API creates the application session foundation.
Flynn records the installation when Discord returns server details.
Flynn opens the Setup Assistant choice for the server owner.

This page starts the public installation journey. Flynn validates the authorization response through the backend, keeps secrets out of browser code, and starts setup only after the owner chooses a guided path.

Permissions

Why Flynn asks for access

Administrator

May be requested for full setup so Flynn can create and manage approved channels, roles, permissions, and server structure without running into Discord permission limits.

Manage Channels

Used when an approved setup or module needs to create or configure channels and categories.

Manage Roles

Used when an approved setup or module needs to create or assign roles. Discord role hierarchy can still block role actions if Flynn's role is too low.

Moderation permissions

Reserved for moderation modules. These are not used by the current install page.

Flynn should request only the permissions needed for approved installation and enabled features. Sensitive moderation permissions stay tied to future moderation modules.

Flynn may request Administrator permission for full setup so it can create and manage approved channels, roles, and server structure without running into Discord permission limits. Flynn still uses planning, approval, bot execution, verification, and reporting.

Trust and support

Review before installing

Privacy Terms Support

Flynn does not change server structure just because it joined. Setup changes are planned, reviewed, approved, applied, and reported. Future module changes follow the same operating model so owners can understand what happened afterward in setup results and future activity history.