Set up Netrcol on your Fluxer server
Add Netrcol to your Fluxer server in minutes: invite the bot, connect your account, check permissions and role order, then test your first module.
A clear path for new server owners
This guide keeps setup in one place, so you can connect Netrcol, review permissions, and configure each system without jumping between unrelated pages. Move at your own pace and return whenever you need a quick refrence.
Begin with setupAdd Netrcol to your Fluxer server
Start from the Netrcol homepage and use Invite Netrcol to open the Fluxer bot authorization flow. Choose a server you are permitted to manage and review the requested access before confirming. Adding the bot and connecting your personal dashboard account are separate steps; completing one does not replace the other.
Read the invitation stepsConnect your Fluxer account
Open the dashboard and sign in through Fluxer. Use the account that manages the server you want to configure. Authorization should take place on the expected Fluxer pages; do not share a password or bot token in a support message. Connecting your account lets the dashboard identify the servers you can manage.
Open Netrcol DashboardSelect the right server
Choose your community in the server selector before changing settings. If it is missing, check the account you signed in with, your server-management permissions and whether Netrcol has been added. Keep test-server experiments separate from the community where real members will receive messages.
Check the initial setupReview permissions and role order
Different modules need different access. Ticket creation needs channel-management permission, role rewards need role-management access, and announcements need permission to send messages in their destination. Role hierarchy also affects which members and roles the bot can manage. Review these requirements before enabling automatic actions.
Read Permissions & RolesChoose a useful first module
Enable only the systems your community needs. Moderation helps staff handle disruptive behavior, tickets organize individual support requests, and levels recognize participation. Each module has its own configuration. Follow the relevant documentation for detailed setup instead of enabling every feature at once.
Browse module guidesTest, save and review
Save your configuration and try a controlled example with appropriate test roles and channels. Check both the dashboard preview and the message or action that appears in Fluxer. If something is missing, review the destination, module switch and permissions. Once the flow behaves as intended, introduce it to your members and keep the configuration under review.
Troubleshoot common issues