NuBerea Discord Bot Setup Guide

Follow these steps to add the NuBerea bot to your Discord server and enable verified community features with AI chat capabilities.

Prerequisites

• You must have Manage Server permission in your Discord server
• Your server must allow bot additions (check Server Settings → Integrations)

Step 1: Invite the Bot

1. Click the invite link:

   https://discord.com/oauth2/authorize?client_id=1456811250901188609

2. Select your Discord server from the dropdown menu
3. Review the permissions the bot is requesting
4. Click “Authorize” to add the bot to your server

Step 2: Verify Bot Installation

1. Go to your Discord server
2. Look for “NuBerea joined the server” message in your system channel
3. You should see the NuBerea bot appear in your member list (right sidebar)
4. The bot should have an online status (green indicator)

Step 3: Test the Bot

Try the AI chat command:

/nuberea-chat message: What does Genesis 1:1 say?

Step 4: Configure Linked Roles (Optional)

Set up automatic role verification to gate channels based on NuBerea account ownership.

A. Enable Linked Roles

1. Go to Server Settings → Linked Roles
2. Click “Add a Requirement”
3. Search for “NuBerea” in the connections list
4. Click “Connect” to link your server to NuBerea

B. Create a Verified Role

1. Go to Server Settings → Roles
2. Click “Create Role”
3. Name it (e.g., “Verified Member”, “NuBerea User”)
4. Set permissions for this role (e.g., access to verified-only channels)

C. Add Verification Requirements

1. Edit your newly created role
2. Go to “Links” tab
3. Click “Add Requirement”
4. Select “NuBerea” as the connection
5. Choose criteria:
   • “Has NuBerea Account” = true (user must have linked account)
   • “Account Created” > 30 days ago (optional: prevent new/spam accounts)
6. Click “Save Changes”

D. Create Verification Channel (Optional)

Create a dedicated channel for users to complete verification:

1. Create a new text channel (e.g., #verification)
2. Set permissions so @everyone can only see this channel
3. Pin a message with instructions:

   Welcome! To access the full server, link your NuBerea account.
   
   1. Go to Server Settings → Linked Roles
   2. Find "NuBerea" and click "Connect"
   3. Follow the OAuth flow to link your account
   4. Return here and you'll automatically receive the Verified Member role!

Step 5: User Verification Flow

When a user connects their NuBerea account:

1. User clicks “Connect” in Server Settings → Linked Roles
2. Discord redirects to NuBerea OAuth authorization
3. User authorizes with their Discord account (grants role_connections.write permission)
4. User logs in to NuBerea (Google, Apple, Discord)
5. Discord metadata updated - Bot updates user’s verification status
6. Role automatically granted - Discord assigns the configured role
7. User gains access - Can now see verified-only channels

Available Commands

/nuberea-chat

Description: Chat with the NuBerea AI assistant

Usage:

/nuberea-chat message: [Your question or message]

Examples:

/nuberea-chat message: Who was King David?
/nuberea-chat message: Explain the parable of the Good Samaritan
/nuberea-chat message: What does the Bible say about forgiveness?

First-time user flow:

• If not linked, user receives a prompt to connect their account
• After linking, command can be used immediately

Response format:

• AI-generated answer based on Biblical context
• Relevant scripture references
• Study resources and related topics

Troubleshooting

Bot appears offline

• Check if the bot has been kicked or banned
• Verify bot status at: https://discord.com/developers/applications
• Contact support if bot is persistently offline

Linked Roles not working

1. Ensure you’ve registered the metadata schema (admin task)
2. Verify the bot has applications.commands permission
3. Check that users have completed the full OAuth flow
4. User may need to refresh Discord (Ctrl+R / Cmd+R)

User can’t verify

• Ensure user has a NuBerea account (sign up at NuBerea website)
• Check that OAuth endpoints are responding (check bot logs)
• User should try disconnecting and reconnecting in Discord settings
• Clear browser cache if stuck on OAuth redirect