What happens after I connect Discord?

Choose the channels you want to publish. Velumn turns their public threads into readable web pages, keeps edits and deletions in sync, and links every page back to the original Discord conversation.

Does this replace Discord with another forum?

No. Your members keep asking, answering, and participating in Discord. Velumn gives selected public threads a companion website so people outside your server can discover them.

What content becomes public?

You choose which channels Velumn indexes. It publishes public-thread content the bot can access rather than mirroring every message in your server. Public pages omit Discord avatars and tags, and members can anonymize their displayed names.

Can I publish on my own domain?

Yes. You can connect a verified custom domain so your community knowledge lives under your own brand, with its own canonical URLs and sitemap.

For communities with answers worth sharing

Help more people find
your Discord community.

Velumn turns selected Discord threads into public, search-friendly pages. Readers find the answer on the web, then continue the conversation in your server.

Start free trial

7 days free. No credit card required.

Northstar Community

community.northstar.dev

Search community

Community operations / Permissions

How should I structure roles for a growing Discord community?

Published from Discord · #community-help

MayaOP• today at 10:42

We have moderators, contributors, and several project teams now. How do we keep permissions understandable as the server grows?

1 Reply

Rowan• today at 10:51

Start with a small set of permission roles: admin, moderator, member, and bot. Keep channel visibility separate from moderation access, then test each role with a non-admin account before adding exceptions.

Continue the discussion

Open the original thread

Open in Discord

One thread. More ways to discover your community.

Velumn handles the public page. Your members keep using Discord.

Search-readyWeb-accessibleDiscord linked

See a live Velumn page

Discord knowledge

Your community creates value every day. Make it compound.

Every solved problem can help the next member, reduce a repeated question, and introduce someone new to your community. It just needs to survive the timeline.

Get found beyond Discord

Give selected public threads readable pages with search-friendly metadata and stable URLs.

Make every answer last

Keep useful solutions accessible after the Discord timeline has moved on.

Bring discovery back home

Show readers the community behind the answer and send them into the original conversation.

A useful answer should keep working long after the Discord thread goes quiet.

From thread to web

It starts with a Discord thread.

No copying answers into a help center. No second community to run. Choose the channels that matter and let useful conversations keep working after they end.

Your community solves a problem

maya · today at 10:42

How should I structure permissions for a community server?

Velumn gives it a durable page

The complete conversation

Search-friendly structure

A direct path back to Discord

The answer keeps working

Discord community permissions

velumn.com › thread

How to structure permissions for a community server

#general

Not connected

#help-and-support

Index public threads

#product-feedback

Index public threads

#team-only

Not connected

Publishing controls

Publish the knowledge. Keep control of the source.

Choose the channels Velumn indexes instead of mirroring your entire server. Public pages stay in sync with message edits and deletions, while members can anonymize their displayed names.

Channel-level publishing controls

Edits and deletions stay in sync

Velumn for AI

Give AI tools a source they can actually access.

Answers locked inside Discord are invisible to the open web. Public Velumn pages create stable source material that AI tools may reference when answering related questions.

Web-accessible, structured source pages

Original context and community stay attached

ChatGPT

Answer with sources

How should I structure permissions for a community Discord?

Start with role-based access, keep administrative permissions separate, and make public support channels readable without exposing private areas.

Sources:

A practical permissions model for Discord

High

Publicly inspectable

Trust starts with code you can inspect.

Velumn's source is public. See how your community pages work, review every change, and report issues directly on GitHub.

Inspect the source

$ git clone velumn

Cloning into 'velumn'...

remote: source available for inspection

Receiving objects: 100% complete

Ready to inspect

Before you publish

Your Discord stays yours.

Velumn adds a public layer to selected threads without changing where your community talks.

Your community already has answers worth finding.

Turn selected public threads into durable pages that keep helping, keep earning trust, and keep leading people back to Discord.

Start free trial

7 days free. No credit card required.