Overview
◈
AdministratorOWNER
Recent activity
Setup checklist
01
Connect your Discord botAdd application credentials, then register slash commands.
02
Approve external serversConnect Last Story or another server via signed webhooks or bot categories.
03
Enable Tebex reportingConfigure the Tebex webhook secret, endpoint and payment events.
04
Publish from GitHubDeploy the site and bot to an always-running host.
MULTI-SERVER SUPPORT
Support tickets
Tickets arriving from approved webhook integrations or watched Discord categories.
| Ticket | Server | Status | Assigned | Updated |
|---|
FFD SERVICE DESK
Development requests & chat
Reply to requests submitted on the website. Online presence is opt-in and expires when your dashboard is inactive.
Live agent availability
When enabled and this tab is active, visitors will see live staff availability. Messages remain private even while offline.
Offline by default.
Incoming service requests
Select a request
Choose a customer to view their conversation.
EXTEND YOUR SUPPORT NETWORK
Connected Discord servers
Add Last Story or any other server individually. Each connection is private, restricted and disabled by default.
Create webhook connection
Only connect ticket systems whose owner has authorized forwarding. The source system must support outgoing HTTP webhooks or a small signed relay.
Copy this connection secret now — it cannot be displayed later.Signing: HMAC-SHA256 of
Endpoint
Signing secret
timestamp.event_id.raw_json_body, headers X-FFD-Timestamp, X-FFD-Signature, and X-FFD-Event-Id. Activate the connection below when the source is ready.Connections 0
Bot connection (no HTTP relay required)
An administrator in another Discord server can install FFD Manager, then run /ffd-connect category:#their-ticket-category label:Last Story. You approve the request here. This mode synchronizes ticket channel creation/closure, not conversation text or attachments. They can revoke it using /ffd-disconnect.
VERIFIED STORE ACTIVITY
Open Tebex creator panel ↗Tebex sales reporting
Signed payment events — successful purchases, refunds and disputes. Private customer details are not stored.
Completed revenue by currency
Only completed, non-refunded/non-disputed payments are included. These are transaction amounts, not earnings after fees or payouts.
Waiting for a verified Tebex event.
Recent transactions
| Transaction | Items | Amount | Status | Date |
|---|
How sales connect
In Tebex Creator Panel, add /api/webhooks/tebex on your published domain. Select payment completion, refunds, and disputes. Set TEBEX_WEBHOOK_SECRET on your host to match Tebex’s signing secret. This dashboard cannot issue refunds or edit payout details.
SEASONAL DESIGN SYSTEM
View live website ↗Website themes
Switch the visual style instantly or schedule it automatically by season. Upload new artwork without redeploying.
Seasonal artwork manager
Change the hero background, featured logo, or promotional image. Uploads are restricted to PNG, JPG or WebP (maximum 6 MB). Files are stored in the host's persistent data volume.
DISCORD MANAGEMENT
Open Discord ↗Community tools
Post professional announcements through the FFD bot and open the connected server.
Publish announcement
Posts to the announcement channel selected below. The bot must be online, and you must confirm the action.
Configure and organize the FFD server
Checking bot connection…
Official FFD home server
Fixes "Unknown Guild" when the bot is connected but DISCORD_GUILD_ID is wrong. Select only a server you personally administer. This does not change Last Story's authorized ticket connection.
Use "Check server layout" to see the exact changes before applying them.
Only the original FFD Discord can be organized from here. Last Story and other servers can opt in to ticket metadata, but the dashboard never edits their channel permissions or sends messages there.
Existing Discord slash commands
/setup preview · /setup apply · /panel support · /ticket open · /announce · /release. The setup command previews all proposed changes first and does not delete channels.
OWNER ACCESS CONTROL
Admins & staff
Invite staff using a Discord user ID. Permissions take effect when they log in. Your original owner account cannot be removed here.
Give dashboard access
Enable Discord Developer Mode to copy a user's ID. Staff must sign in using their own Discord account. No password or bot role is needed.
Current staff access
0| Discord account | Access role | Granted | Controls |
|---|
Access policy
Only the original owner can manage staff. Administrators manage operations but cannot add other admins. Support Staff see tickets and service requests; Sales Staff see Tebex sales; Designers manage themes. Changes and revocations are recorded in the activity audit.
REAL INTEGRATIONS ONLY
Go-live status
Configuration and recent event details. Missing credentials are never replaced with fake products or simulated orders.
Connection addresses
Copy these into the Discord developer portal and Tebex Webhook settings after assigning your live HTTPS domain.
Security and sales scope
Credentials live on the server in environment variables, never in the public frontend or a GitHub commit. Sales appear only when Tebex sends a cryptographically verified event after connection; previous orders do not automatically import. Product edits, chargebacks and refunds must be handled in the Tebex Creator Panel.