Branding
Customize the OpsPilot365 platform appearance with your organization’s branding. Apply consistent visual identity across the admin console, client portal, and all outbound communications.
Platform Branding Options
Customize the following elements of the MSP admin console:
| Setting | Description | Recommendation |
|---|---|---|
| Logo | Company logo displayed in header and login page | PNG or SVG, transparent background |
| Favicon | Browser tab icon | 32x32px ICO or PNG |
| Primary color | Main accent color for buttons, links, and highlights | Use your brand hex color |
| Login background | Custom background image for the login page | High-res, 1920x1080 minimum |
| Company name | Organization name shown in the header and page titles | Your brand name |
Client Portal Branding
The client-facing portal can be branded separately from the admin console. This allows you to present a distinct look to your customers.
- Client portal logo — Separate logo for customer-facing pages
- Client portal colors — Independent color scheme for the client experience
- Custom login page — Branded login experience for client portal users
- White-label email notifications — All automated emails use your branding
Note: Client portal branding is configured separately from platform branding. Changes to platform branding do not affect the client portal, and vice versa.
Notification Branding
All outbound notifications can be branded with your identity:
Email Notifications
- Custom sender name and reply-to address
- Your logo in email headers
- Brand colors in email templates
- Custom footer with your support contact information
Teams Notifications
- Adaptive cards display your logo
- Brand-colored notification cards
- Custom bot name if using Teams connector
Notification Channels
OpsPilot365 supports three notification delivery channels:
| Channel | Features |
|---|---|
| Individual recipients, distribution groups, HTML or plain text, digest mode | |
| Microsoft Teams | Channel webhooks, adaptive cards, actionable messages, thread replies |
| Webhooks | Custom endpoints, JSON payloads, custom headers, retry logic |
Notification Categories
Configure notifications by severity and category:
| Category | Severity | Example Events |
|---|---|---|
| Security Alerts | Critical | Risky sign-in detected, user at risk, malware blocked |
| License Alerts | High | Low license threshold, subscription expiring, over-allocation |
| Service Health | Medium | Service degraded, outage detected, maintenance scheduled |
| Compliance | High | Device non-compliant, Secure Score dropped, DLP violation |
| Operations | Low | Sync completed, workflow executed, report generated |
Notification Rules
Create custom rules to route notifications based on conditions:
| Rule | Condition | Channel | Status |
|---|---|---|---|
| Critical Security | severity = critical AND category = security | Teams, Email | Active |
| License Threshold | category = license AND available under 10% | Active | |
| VIP Tenant Alerts | tenant.tag = “VIP” | Teams, Webhook | Active |
Quiet Hours
Suppress non-critical notifications during specified hours:
- Schedule — Define quiet hours per day of week. Critical alerts are always delivered.
- Deferred Delivery — Suppressed notifications delivered as a digest when quiet hours end.
Best Practices
- Keep branding consistent between admin console and client portal
- Use high-resolution images for logos to ensure crisp display on retina screens
- Test email notifications after changing branding to verify rendering
- Ensure your primary color has sufficient contrast for accessibility
- Update branding across all channels when rebranding
API Reference
GET /api/msp-portal/settings/branding— Get current branding settingsPUT /api/msp-portal/settings/branding— Update platform brandingGET /api/settings/notifications— Get notification settingsPUT /api/settings/notifications— Update notification settingsGET /api/settings/notifications/rules— List notification rulesPOST /api/settings/notifications/test— Send test notification