Server settings

Every setting for a server in Colossus, from the bot and its intents to the time zone, data retention, what is not recorded, the history import, turning levelling on, and deleting a server.

Settings, at the foot of the sidebar, holds everything about how Colossus runs for a server, on Server, Import, Team and Plan & billing. The sections below are on Server, except the history import, which is on Import, and Activity, which is on Team. You see the pages and sections your access allows. Without permission to change a setting you see its current value instead of the control.

Server

  • Connected server and Bot show which Discord server this is and which bot records it. Install link opens Discord to add the bot again.
  • The three intent rows show whether the bot receives Server Members, Message Content and Presence data. Each one feeds different cards; when one is off, those cards say so.
  • Show this server on colossus.dislace.com lets your server's name and icon appear among the servers using Colossus. It is available on the shared bot.

On Titan you can run the server on your own bot:

  • Your own bot moves the server from the shared bot to a bot application you created, with its own name and avatar. Press Connect your own bot and follow the steps: create the application, switch on the three intents, invite it to your server, then paste its token and press Move to your bot.
  • Shared bot moves back to the shared bot. Add the shared bot on Discord first.
  • Privileged intents links to the Discord developer portal, where your bot's intents are switched on. Press Check now after changing them.
  • Switch server points the dashboard at another Discord server your bot is already in. Everything recorded about the current server is deleted, and the new one starts from nothing, so it asks you to type the server's name first.

If the bot is removed from your Discord server, Colossus stops recording and this section says so. The server's data is kept for 90 days; press Invite the bot back within that time to carry on where you left off.

Data

  • Analytics timezone: the time zone every chart's days and hours follow.
  • Keep analytics for: how long analytics are kept, from 90 days to everything. Shortening it deletes older analytics for good, so it asks you to type the server's name. Your plan decides how far back charts show; this decides how long data is kept.
  • Not recorded: channels, categories and roles Colossus does not record, below.
  • Member opt-out: members can type /opt-out in Discord to be erased from Colossus for your server, their levels included, and /opt-in to be counted again from then on.

History import

On Pro and Titan, Colossus can read your server's past messages, so charts start from its history instead of the day you added the bot. It is Analytics history, the first section of Import, under Settings; the section after it, Levelling history, is for moving over from another levelling bot. You see Import if you may see history imports, and start or stop one if you may run them. The import reads every channel, thread and forum post the bot can see, newest first, and runs in the background.

Before an import, the section says how far back your charts go. Press Import history to start it, or Cancel import to stop. While it runs, the section shows how many channels, threads and forum posts are done and how many messages it has read, and the top bar of every view shows the same count of channels, which opens the section when pressed. When it ends, the section says how it ended and when, how far back it reached and how many messages it read. Channels the bot cannot read the history of are skipped, and those that kept failing are given up on; each count has its own row.

Setup ticks the import for you on Pro and Titan, so most servers have it running from the first day.

What is not recorded

Not recorded stops Colossus recording some of your server:

  • Channels and categories. A category covers its channels now and in future, and threads and forum posts follow their parent channel. Use it for private staff channels, or bot spam channels you do not want in your numbers.
  • Roles. Members with an excluded role are not recorded anywhere.

Changes apply from then on, and what was already recorded stays. To remove it too, press Delete recorded history beside an excluded channel or category, which also deletes the levelling XP earned there. Colossus cannot exclude individual members; members can opt themselves out instead.

What is not recorded earns no levelling XP either.

Modules

Modules lists what Colossus runs for the server. Analytics is always on. Levelling switches levelling on and off; you need permission to change levelling. Turning it on works out every member's level from what is already recorded, announcing nothing, and asks first if it would give or take reward roles. Once it is on, the row lists the permissions level-ups and reward roles need from the bot. See Levelling.

Activity

On Pro and Titan, Activity lists who changed access, handed over ownership, changed the plan, moved the bot or deleted the server, and when.

Danger zone

  • Bot token: on your own bot, store a new token after resetting it in the Discord developer portal. Press Store new token; the token is checked with Discord, stored encrypted and never shown again.
  • Hand over ownership: make someone else the owner. See Give your team access.
  • Delete this server: remove the server from Colossus, with everything recorded about it. Your Discord server itself is untouched. You type the server's name to confirm, and it cannot be undone.