Questions community owners ask before connecting PulseMDT

Yes. PulseMDT does not divide the CAD, MDT, civilian portal, or connected FiveM features into paid tiers. The service may use advertising on public informational pages to help cover operating costs, but ads are not placed inside authenticated CAD, dispatcher, admin, or sign-in workflows.

You need a Discord community, an account authorized to connect it, clearly defined staff and department roles, and a FiveM server only if you plan to use the in-game integration. We recommend deciding rank, callsign, penal-code, warrant, and report rules before inviting the full staff team.

Discord identity, guild membership, configured Discord roles, selected community, department type, and feature settings are used to determine access. Sensitive API routes repeat authorization checks on the server. Hiding a navigation item is not treated as sufficient permission control.

Broad Administrator permission should not be the default. Grant the bot role only the permissions needed by the modules you enable, place it above roles it must manage, and test the result with a normal staff account. Community ownership and high-trust administrative roles should remain above the bot.

The public PulseMDT service and web dashboard are operated by Pulse Systems. Your FiveM server installs the connected Pulse resources and holds its own community API key. Server owners should keep that key private and follow the published release instructions when updating resources.

PulseMDT includes a standalone character framework and connected resources designed around the Pulse data model. Individual integrations can have different prerequisites, so check the current documentation and release notes before combining them with another economy or character framework.

Connected resources cache supported settings and lookup data so a short interruption does not immediately stop ordinary play. Supported writes can synchronize when service returns. Staff should preserve the first error, check the public status page, and avoid repeatedly restarting resources or rotating keys unless authentication is the confirmed cause.

No. Records and configuration are scoped by the selected Discord community, and authenticated actions are checked against that scope. Community administrators are responsible for their own role mappings and for removing access when a staff member changes roles or leaves.

Do not store real criminal records, medical records, addresses, government identifiers, passwords, payment information, or other real sensitive personal data. PulseMDT is intended for fictional FiveM roleplay characters and community operations, not real-world emergency or law-enforcement work.

There is no universal one-click importer because CAD schemas, permissions, and record meanings differ. Preserve the old system during rollout, identify the records that are genuinely needed, and contact support before attempting a migration. Avoid copying stale or duplicate records simply to make the new system look complete.

Keep it in server-only configuration, never client Lua or NUI code. Do not commit it to a repository or paste it into public support channels. Use separate keys for development and production, rotate keys when infrastructure access changes, and revoke immediately if exposure is suspected.

Email [email protected] with the affected route or resource, expected behavior, actual behavior, approximate time, and relevant log lines after removing API keys, tokens, webhooks, and personal data. Security reports should explain the impact and reproduction steps without testing against communities you do not control.

Advertising may appear only on substantive public pages such as product information and guides. Google and its partners may use cookies or similar identifiers subject to consent and regional requirements. Authenticated operational screens are intentionally excluded from AdSense loading. The Privacy Policy explains the providers and available controls.