Your voice channel.
Right in the island.
Connect the Windows desktop app, see your voice channel and members, and control your microphone from Notchify. Set up camera and screen-sharing shortcuts once, using the keys you already prefer.
Use Discord desktop on Windows. Microphone and audio controls use the desktop connection; camera and sharing send your configured keyboard shortcuts. Calls use Discord’s built-in shortcuts.
Start in Discord’s Developer Portal.
- Open the Discord Developer Portal and sign in with the same Discord account you use in the Windows desktop app.
- Select New Application. Enter a name you will recognize, such as Notchify Connection.
- Read and accept Discord’s developer terms if prompted, then select Create.
- On General Information, find Application ID and select Copy. This is the ID Notchify calls Client ID. Keep it for the connection step.
You are creating an application entry for the local connection. You do not need to create a bot, copy a Bot Token, or invite a bot to a server.
Two values. One redirect.
- In your application’s left sidebar, select OAuth2. If a submenu appears, open General.
- Under Client Information, copy the Client ID. It is the same value as Application ID.
- Find Client Secret. Use Reset Secret to generate a secret if one is not shown. Complete Discord’s account verification if requested, then copy the newly revealed value.
- Under Redirects, select Add Redirect, enter exactly
http://localhost, and select Save Changes.
Do not add a port, an HTTPS prefix, or a trailing slash. Client Secret is not Public Key or Bot Token. Resetting a secret invalidates the previous secret; update Notchify if you reset it later.
Paste your secret only into the installed Notchify application. This guide never requests, receives or stores real credentials. Never share a screenshot containing an unmasked secret.
A one-time desktop connection.
- Open and sign in to the Discord desktop app for Windows. A Discord browser tab alone does not provide the desktop connection.
- In Notchify, select the Discord icon in the toolbar, then the settings gear → Connection.
- Paste the Client ID and Client Secret from your own application. On first setup both are required; leave the secret blank only when it is already saved.
- Select Save and connect. In Discord’s authorization prompt, check that the application name matches the one you created, then select Authorize.
- Return to Notchify. When it shows Desktop connected, join a voice channel in Discord to see the channel and members.
Treat your Client Secret as a password. Do not paste it into chats or screenshots. Saved credentials are protected with Windows encryption for your Windows account. A valid session is reused on restart; Discord can still require authorization if access expires or is revoked.
Give Discord the actions first.
Open User Settings → Keybinds → Add a Keybind in Discord. Add separate actions for Toggle Camera and Toggle Screen Share, using the labels available in your client language.
Record a distinct combination for each. These are examples, not required keys:
Close Discord's Keybinds settings before testing. Discord disables keybinds while that page is open.
Discord's screen-share action can toggle an existing broadcast and may only start sharing when it recognizes a game. It does not guarantee an arbitrary window picker. If needed, start sharing and choose the screen or window directly in Discord.
Same keys. No guessing.
Return to the Discord settings inside the island. Select the Shortcuts tab, then click the key field for an action and press the exact combination you assigned in Discord. It saves automatically.
- NumPad 2 is different from the 2 above the letters. Record the actual physical key you use.
- Use the × next to a shortcut to clear it.
- Enable Bring Discord to front if that action needs focus. Camera uses this by default; global screen-share shortcuts can work without it.
- Camera and sharing are unassigned on new installations until you record them. Existing configurations keep their previous shortcuts.
These fields configure what Notchify sends. They do not change Discord's own keybind settings.
Try one action at a time.
Join a voice channel, close Discord's settings, and open the Discord tab in Notchify. You should see your channel and its members.
- Microphone and headphones use the desktop connection directly.
- The camera button sends your saved camera shortcut. If you enabled focus, Discord is brought forward first.
- The share button sends your saved sharing shortcut. Any screen or window selection still happens in Discord.
Testing camera or screen sharing can make your camera or screen visible to people in the channel. A “Shortcut sent” status confirms key delivery, not that Discord completed the action.
Answer from the call popup.
Notchify detects incoming Discord calls from Windows notifications and shows Accept and Decline controls when Discord desktop is connected.
Discord’s built-in shortcuts are Ctrl + Enter to accept and Esc to decline. These are fixed, not custom keybinds you need to create. Notchify brings Discord to the front before sending them.
Allow Discord notifications in Windows and Notchify's notification access. Detection depends on the notification Discord emits and can vary with language and client version. Test these controls with an incoming call after completing setup.
When something does not respond.
Where do I find Client ID and Client Secret?
Developer Portal → your application → OAuth2 → Client Information. General Information → Application ID is the same Client ID. Generate or reset the Client Secret in OAuth2, then save http://localhost under Redirects. Public Key and Bot Token are different values.
The connection is waiting or authorization fails.
Start Discord desktop and sign in. Check the application ID, current secret, and exact http://localhost redirect in the Developer Portal. If you reset the secret, update Notchify too. A developer application can be subject to Discord's RPC access restrictions; an ID alone cannot grant missing permissions.
The camera or sharing button does nothing.
First press the same keys yourself in Discord, with its Keybinds settings closed. If that fails, fix the Discord assignment first. Then record the same physical keys in Notchify, check NumPad versus top-row digits, and try the foreground option. Make sure both apps run at the same permission level. Screen sharing also depends on Discord's game detection and current broadcast state.
Discord comes forward, but the camera stays off.
Check whether you recorded NumPad 2 or the top-row 2. They are different keys. Join a voice call and test the exact combination manually, then record it again in the island. Avoid conflicts with other shortcuts.
I do not get incoming-call buttons.
Make sure Discord notifications appear in Windows and Notchify can read notifications. A connected Discord desktop session is required. If Discord emits no recognizable call notification, Notchify cannot reliably show this popup. A normal message notification is not an incoming-call notification.
Does the setup need authorization after every restart?
It should reuse a valid saved session. Notchify stores credentials encrypted for your Windows user and refreshes access when possible. Revoked permission, changed application credentials, deleted settings, or a failed refresh may require you to reconnect explicitly.
Independent Notchify guide. Discord is a trademark of Discord Inc. Interactive demonstrations follow the Notchify interface and use fictional account details. Developer Portal labels may change with Discord updates. Further reading: Discord's keybind guide, Windows hotkeys, and Go Live and screen sharing.