Skip to content
Join A.R.X.

A.R.X. guides / 06

Set up your Discord community

Connect the right account, choose your server and review the setup before confirming a build.

Practical steps · Updated 7 October 2026

01

Use a regular A.R.X. account

Create or sign in to your A.R.X. account. A server manager does not need a developer or client profile, portfolio or marketplace verification to use community setup.

Open Set up your Discord server. Link the Discord account you use to manage the intended server.

02

Select a server you are authorised to manage

Follow the dashboard’s server selection and access checks. The server owner and A.R.X. operator can assign manager or reviewer roles. Manage Server alone does not grant access to the network staff controls.

Use the dashboard’s install link when the bot needs to be added. Discord account linking identifies you; installing the bot authorises it for that server. Follow the displayed permissions and approval requirements.

03

Preview the layout before confirming

Choose the feeds and destinations the dashboard offers. Review the layout preview, including channels and existing-layout reuse, before requesting or confirming a build.

The console shows when community approval or further access checks are needed. An install or preview does not mean the layout has been approved or created.

Live server layout refers to your actual feed destinations. A private test area contains empty channels and threads for checking the structure. Finishing the test returns to live controls; deleting the test area is a separate confirmed action.

Fresh-server builds still require community approval, server authority and explicit build confirmation. Broader rollout remains a pilot; existing A.R.X. and KW Studio feed setups are working.

04

Set rules, staff and local review

Open Rules and staff. Choose incoming feeds and outgoing submissions independently. Set allowed categories, compensation types, comparable minimum budgets, required details, posting limits and cooldowns. Use the ? beside a label for its meaning and limits.

Owners can assign approved manager and reviewer roles. Managers configure policies; reviewers handle local moderation. Permissions are checked again when an action is performed.

Choose the incoming approval mode. Written rules require local review even when an automatic mode is selected. A trusted source must still meet the remaining rules and the author’s sharing choice.

Use Incoming reviews to check exact listing terms before approval, reject an entry or remove its local copy. Author/source blocks and network reports handle repeat problems. A.R.X. approval does not override your server’s rules.

Author ID is the A.R.X. website user number shown on the incoming entry. Source server ID identifies the originating Discord server. Follow the adjacent help before adding a block.

Use Activity to review actions and delivery status. Verify destinations with the community team before treating setup as complete.

05

Enable voluntary member submissions

Outgoing submissions are off by default. Enable them only when your community is ready and choose whether staff must approve outgoing drafts.

Members with an eligible linked A.R.X. account can use /arx post to start a private, structured listing draft. They explicitly choose website + originating server or website + participating communities. Normal chat messages are never imported.

Use /arx listings to return to drafts and listings, /arx search to browse, and /arx help for personal tools. Authorised staff can use /arx manage. The website’s Member submissions panel tracks outgoing submissions and any required local review.

Local approval, A.R.X. publication review, author consent and each receiving server’s rules still apply. Test one agreed listing through creation, review, edit and withdrawal before expanding the pilot.

06

Get setup help

For approval, installation or delivery questions, choose Discord community setup on Support. Include the server and the setup stage where you are stuck.

Read Account connections for the difference between a linked identity, public profile visibility and private activity notifications.