BRAD Cloud Services

BRAD Cloud supplies shared services to connected applications. Open BRAD Cloud for your account's active services and their controls. A cloud service is separate from your CMS hosting subscription and software license.

Activate and confirm a service

Choose the cloud product you need from the available catalog, complete checkout, and confirm that its service is active. The portal creates a wallet when the first cloud service is activated.

For use inside the CMS, configure or connect the corresponding provider there. Purchasing a cloud service does not by itself prove that the CMS is connected or that all sending requirements are complete.

Fund and monitor the wallet

Open Wallet. Review the balance and recent ledger activity. A manual top-up creates an invoice; credit is posted after the invoice is fully settled. If an unpaid top-up already exists, resolve it in invoices before creating another.

Configure:

• Low-balance warning: when the balance should be flagged as low.
• Daily spend cap: the permitted daily spend shown by the wallet settings.
• Automatic top-ups: whether to use your saved payment method.
• Top-up threshold, amount, and daily maximum: when and how much automatic funding can add.

Save changes and recheck the displayed values. A spend cap and an automatic top-up limit control different things: one limits usage spending, the other limits added funds. Confirm payment availability before relying on automatic top-ups.

Open Usage to review recorded activity. If sending stops, check service activation, balance, cap, provider setup, and delivery errors before repeatedly retrying the same workload.

Verify a sending domain for BRAD Mail

1. Activate the BRAD Mail service.
2. Open Sending Domains.
3. Add the domain you intend to send from.
4. Open DNS records and copy the required names, types, and values to the authoritative DNS provider.
5. Use the verification action after the records are visible.

Preserve existing records for your other email services. Domain ownership and sender authentication are different from registering a domain or pointing your CMS website at a host. Verify the sending domain before depending on it for account recovery or production notifications.

Manage credentials

Open API Keys to create credentials for authorized integrations and review available webhook controls. Use an identifiable label and only the scopes required by the integration. Copy a newly issued secret when shown and store it in your application's secret configuration.

Do not expose keys in browser code, public repositories, or tickets. Revoking a key immediately affects integrations using it. Prepare a replacement, update the application, verify successful requests, and then revoke the old credential.

Confirm the CMS connection

In the CMS, check the selected communication or cloud provider and its connection state. Test one small operation, verify delivery or completion, and review the corresponding portal usage. Keep the CMS's public HTTPS URL correct so signed callbacks can reach the installation.

The integration setup guide covers the operational checks. Detailed provider and module usage remains in the CMS documentation.