Integration Setup

Configure providers from their categories under Settings in the CMS. Enable only the integrations your organization needs, and verify each one with a small test before depending on it.

These checks concern deployment and readiness. Provider-specific fields and daily use are documented inside your CMS.

Outgoing email and SMS

Open Communication Providers. Select the provider that fits your account, such as BRAD Mail, SendGrid, SMTP, or an applicable SMS provider, then supply its required credentials and sender information.

Before launch:

1. Verify the sender or sending domain with the provider.
2. Confirm the selected provider is enabled and used for the intended communication channel.
3. Send a test to an inbox outside your own domain.
4. Check delivery results, not just whether a request was accepted.
5. Test a password-reset message and verify that its link uses your public HTTPS domain.

For BRAD Mail, also verify the cloud wallet and sending domain. For providers with delivery callbacks, configure their required endpoint and signature verification information. The CMS must be reachable publicly over HTTPS for callbacks.

Never use a localhost APP_URL in production. It can produce unusable recovery links and callbacks even though the homepage works.

File uploads

Open File Uploads and choose the supported provider and settings appropriate for your installation. Decide where files are stored, what types and sizes to accept, and who maintains the backup.

For local disk, APP_ROOT determines the base of storage/uploads. Give the application user write permission and ensure the location persists across deployments. For an external provider, verify credentials, access controls, and the provider's retention and backup arrangements.

Upload a small file, load it from another browser, then restart the app and confirm it remains available. A database backup alone does not protect externally stored file contents.

Payment collection inside the CMS

Open Payment Gateways if your organization will collect payments through CMS modules. Configure the gateway and its callback or webhook requirements, then complete a test payment in the provider's test environment.

CMS payment credentials are separate from the Stripe account the BRAD portal uses to bill your organization. Do not reuse portal configuration values simply because both systems support Stripe.

Verify success, failure, and cancellation behavior and the resulting CMS records before switching to live keys. Check that the public callback URL and signing secret belong to this installation and environment.

Streaming, conferencing, and AI

Configure these only when your selected modules require them. Streaming and conferencing serve different uses and can have different providers. Match credentials, URLs, and limits to the selected service.

For externally billed providers, assign someone to monitor quotas and costs. Where available, use restricted credentials and a separate test environment.

Keep a provider inventory

Record each enabled provider, its purpose, account owner, sender or endpoint, renewal or spending responsibility, and date of the last successful test. Store secrets separately.

After rotating a credential or changing a public URL, restart where required and repeat the affected integration test. Use troubleshooting if provider requests succeed but results do not reach users.