A permission on the voice channel beats the permission on the role — and administrators bypass it.
So you test it, it works, and you conclude the app is fine. It is. What is not fine is
Use Activities on the channel your members are sitting in. Because you are an
admin, you will never see the failure yourself.
Check Edit Channel → Permissions on the voice
channel and on the category above it. If Use Activities is a red deny for
@everyone or for their role, that is your bug. Set it to neutral or allow.
Temp voice channels
If your server creates voice channels on demand — a “join to create” hub, or any temp-channel bot — read this before anything else, because fixing the symptom does not hold.
Those channels are clones. The bot copies the permission overwrites of a hub or template
channel every time it makes a new one. If the hub denies Use Activities, every
channel it spawns is born denying it. You can fix a live temp channel, launch the map happily,
and then the next channel your members create is broken again — which looks exactly like the
app being flaky.
Fix the hub, not the children. Find the channel your bot clones from (its configuration will name it — often a category template, or the “join to create” channel itself) and clear the deny there. Then delete an existing temp channel and let the bot make a fresh one to confirm it inherited the fix.
Some temp bots also give the channel’s creator extra permissions the other occupants do not get. That produces a very specific symptom: whoever made the channel can launch, and nobody who joins it can.
The test that finds it in one minute
Do not change any more settings until you have run this. It separates “a channel problem” from “a server problem” and takes about a minute.
- Create a new permanent voice channel.
- Drag it to the very top of the server, outside every category, so it inherits nothing.
- Do not touch its permissions.
- Have someone who is not an admin join it and try to launch the map.
It is a channel or category permission on the channel that failed. Go back to
Use Activities above — and if the failing channel is a temp one, fix the hub.
It is server-wide. Check Server Settings → Apps → Activities — a different page from Integrations — and the app’s own access list under Integrations → wardogs.tech → Manage.
What you are looking at
Three different failures look similar and mean opposite things. Matching yours to the right row saves you an afternoon.
| What the person sees | What it means | What to do |
|---|---|---|
| A card with our logo, tags and a description, and no Launch button | That is Discord’s app listing — what an app you do not have looks like. It is not installed for that person. | An admin installs it to the server (below). Or, right now with no admin: the three dots → Add to my apps. |
| “Failed to Launch Activity” / “Unable to launch activity” | The app is available to them. Something refused the launch, which means permissions. | Use Activities on the channel and its category. |
| “You do not have permissions to use activities in this channel” | Discord telling you the answer outright. | Same — and if it is a temp channel, fix the hub it was cloned from. |
| No Start an Activity button at all (no rocket) | Either they are not in a voice channel, or activities are denied on it. | Join the voice channel first. Then check the channel permission. |
| Works for the owner, nobody else, in every channel | You are an admin and admins bypass channel denies. | Run the one-minute test above. Never test this as an admin. |
Installing it, properly
There are two doors and they do different things. Picking the wrong one is a quiet way to end up supporting one person instead of a server.
| Door | Who ends up with it | Use it when |
|---|---|---|
| Add to your server wardogs.tech/add |
Everyone in that server. No bot joins the server, and there are no permissions to approve. | Always, if you can. This is the one you want. |
| Add to my apps three dots on the app card |
Only you — but in every server you are in. | Your admin will not add it, or you need it working in the next thirty seconds. |
To tell which one a server has: Server Settings → Integrations. A server install is listed there, with who added it and when. A personal install is listed for nobody — so if it works for one person and the list is empty, that is your explanation.
Things that are not the problem
All of these have been checked, more than once, and cost real hours. If you are being told one of these is the cause, it is not.
| Suspicion | Why it is not that |
|---|---|
| The app is broken, or down | Hundreds of servers are running war rooms right now. A whole-app failure does not affect one server. |
| It does not support phones | It does. A phone that cannot launch is hitting the same channel permission a desktop would. |
| Your roles are set up wrong | Probably not — and a channel deny would beat them even if they were perfect. Check the channel first, the roles second. |
| The app needs more permissions | It asks for none. No bot joins your server. There is nothing to grant it. |
Still stuck
Bring us the result of the one-minute test — that one fact narrows it further than any description of the symptom can. Tell us your server, whether the person failing is an admin, and whether the channel is permanent or auto-created.