1. Overview
  2. Admin Guide
  3. Branding
  4. Branding Best Practices and Common Scenarios

Branding Best Practices and Common Scenarios

This guide provides practical strategies, recommendations, and solutions for common branding scenarios in DashboardFox. Whether you're setting up departmental branding for your organization, implementing role-based access, or providing analytics to external partners, these best practices will help you make the most of DashboardFox's branding capabilities.

Getting Started: The Right Order

When implementing branding for the first time, follow this sequence for the smoothest setup:

1. Set Your Product Name

Start with the global setting: Settings → Server Settings → Application Settings → Product Name

This establishes the basic identity that appears in browser tabs for all logged-in users. Choose something that represents your organization, department, or function (e.g., "Acme Analytics," "Finance Reporting," "Business Intelligence").

2. Create Default Login Page Branding

Set up Settings → Branding → Login Branding with a default policy (leave Domain Name blank).

This ensures users see your organization's brand from the very first interaction.

3. Configure Guest Branding (if applicable)

If you're sharing public reports or dashboards, set up Guest Branding next. This is global, so you only need one policy.

4. Create Your Application Branding Policy

Set up Settings → Branding → Application Branding

Name it descriptively (e.g., "Company-Wide Branding," "Standard User Policy"), assign it appropriately, and configure the appearance and features.

5. Refine Based on Usage

Once the basics work, evaluate if you need additional policies for different use cases. Contact team@dashboardfox.com if you need to license additional policies.

Working with Single Policy Limits

By default, DashboardFox includes 1 Application Branding policy and 1 Login Page Branding policy. Here are strategies for making the most of these limitations:

Strategy 1: Comprehensive Single Policy

Approach: Create one policy that serves all users with balanced configuration

Best for: Organizations where most users have similar needs

Implementation:

  • Assign to ALL USERS
  • Enable features needed by the majority
  • Use DashboardFox's permission system to control who can create vs. view
  • Configure embedded options for simplified portal views
  • Use per-dashboard/per-report settings for exceptions

Pros:

  • Simple to manage
  • Consistent experience for everyone
  • Easy to onboard new users

Cons:

  • Can't provide dramatically different experiences to different groups
  • May need to compromise on feature availability

Strategy 2: Target Your Primary Use Case

Approach: Optimize branding for your most important user group

Best for: Organizations with one dominant use case and some edge cases

Implementation:

  • Configure branding for your primary user group (e.g., department managers)
  • Assign to ALL USERS or specific primary groups
  • Handle edge cases with per-item settings or workarounds
  • Consider licensing additional policies if edge cases become numerous

Example: If 80% of users are department managers viewing dashboards, optimize for that experience. The 20% who are analysts building reports might need to work around some limitations.

Strategy 3: License Additional Policies

Approach: Purchase additional policies for true segmentation

Best for: Organizations with distinct user groups requiring different experiences

Implementation:

  • Create policies for each major user segment (e.g., Finance, Sales, Operations)
  • Or create policies for different access levels (e.g., Read-Only, Analysts, Admins)
  • Or separate internal users from external partners/customers
  • Assign each policy to appropriate groups

Contact team@dashboardfox.com to discuss licensing additional policies.

Departmental Strategies

DashboardFox's multi-tenant features are geared toward departmental use. Here are proven approaches:

Single Organization, Multiple Departments

Scenario: Your organization has Finance, Sales, Operations, and Executive teams, each with different needs.

With One Policy:

  • Create a balanced policy for most common needs
  • Use DashboardFox's folder permissions to control what each department sees
  • Configure features based on majority use case
  • Use embedded branding to simplify department portal views

With Multiple Policies:

  • Finance Policy: Export and scheduling enabled, SQL view hidden, builder access controlled
  • Sales Policy: Simplified interface, focused on viewing dashboards, no export
  • Operations Policy: Full features enabled, builder access for creating operational reports
  • Executive Policy: Minimal interface, high-level dashboards only, export enabled

Departmental Portals with Embedded Content

Scenario: Each department has a portal page with embedded DashboardFox content.

Strategy:

  • Use one Application Branding policy for base configuration
  • Configure Embed options to simplify interface in portals
  • Keep full features in main DashboardFox app for analysts
  • Use Custom CSS to match each portal's design (if different departments have different portal designs, this becomes a limitation - consider licensing additional policies)

External Partner and Customer Strategies

While DashboardFox is primarily designed for internal use, organizations do provide access to external users:

Strategy 1: Same Branding, Different Permissions

Approach: External users get same branded interface, controlled via permissions

Implementation:

  • Assign external users to the same Application Branding policy
  • Use DashboardFox permissions to control what they can access
  • Create separate folders/dashboards for external vs. internal content
  • Consider hiding advanced features (SQL view, embedding options) if external users don't need them

Works well when: External users need similar functionality to internal users, just with different data access.

Strategy 2: Separate Branding for External Users

Approach: License additional policy for external-facing configuration

Implementation:

  • Create "External Partners" or "Customer Access" policy
  • Simplified interface with limited features
  • Restricted export and sharing options
  • Assign to external user groups

Contact team@dashboardfox.com about additional policies for this scenario.

Strategy 3: Guest/Anonymous Access for External Users

Approach: Use Guest Branding instead of authenticated access

Implementation:

  • Share reports via guest links or embedded guest reports
  • No need for user accounts
  • Configure Guest Branding for external-appropriate interface
  • Simpler management, but less control over individual access

Works well when: External users just need to view specific reports without interactive features.

Embedded vs. Full Application Strategy

Many organizations both embed reports and provide full application access. Here's how to optimize each:

The Clean Embed Approach

In Embedded Content (Embed Options):

  • Hide complexity: Turn off Add Widget, Reorder, Save Views
  • Focus on data: Keep Refresh, maybe Export if needed
  • Simplify visualization: Hide Create Chart
  • Remove administrative options: Hide Schedule, Email

In Full Application:

  • Enable power features: Create Chart, Schedule, Email
  • Allow customization: Save Views, Add Filters
  • Provide full control: All dashboard editing options

Why this works: Embedded content in portals typically has limited screen space and users are focused on specific tasks. The full application is where analysts do deeper work.

Example Configuration

For a typical organization:

Embed Dashboard Options:
- Show Embed Dashboard Details Title: ON
- Show Embed Save This View: OFF
- Show Embed Saved Views: OFF
- Show Embed Add New Filter: ON (useful for filtering)
- Show Embed Refresh Icon: ON
- Show Embed Print Icon: OFF
- Show Embed Export Icon: ON (if users need it)
- Show Embed Add Widget Button: OFF
- Show Embed Widgets Reorder Icon: OFF
- Show Embed Widgets Actions Icon: OFF

Dashboard Options (Full Application):
- All enabled for power users and analysts

Common Scenarios and Solutions

Scenario: IT Team Needs Full Access

Problem: You're creating a policy for general users but IT/analysts need everything enabled.

Solution with One Policy:

  • Configure for majority of users
  • Give IT team direct permissions in DashboardFox to bypass restrictions
  • IT can access features through permission overrides even if hidden in branding

Solution with Multiple Policies:

  • Create "IT & Analysts" policy with all features
  • Create "General Users" policy with restricted features
  • Assign appropriately

Scenario: Users Find Interface Too Busy

Problem: Non-technical users are overwhelmed by too many options.

Solution: Create a minimalist policy:

  • Hide Action Menus where possible
  • Hide Created By, Status columns in Library
  • Hide all editing and customization features
  • Keep only Refresh and viewing capabilities
  • Use Custom CSS to further simplify if needed

Scenario: Compliance Requires No Data Export

Problem: Regulatory requirements prohibit data exports for certain users.

Solution with One Policy: If ALL users have this restriction:

  • Hide all Export options (both embed and application)
  • Hide Print options (can save-as-PDF)
  • Hide Schedule options (emails could forward data)

Solution with Multiple Policies:

  • Create "Restricted Access" policy with no exports
  • Create "Authorized Users" policy with exports enabled
  • Assign based on user authorization level

Scenario: Finance Needs Different Features Than Other Departments

Problem: Finance department needs export and scheduling; other departments don't.

Solution with One Policy:

  • Enable export and scheduling globally in the policy
  • Assign policy to ALL USERS
  • Use DashboardFox permissions to control who can actually schedule and export
  • This approach shows the features to everyone but only authorized users can use them

Better Solution with Multiple Policies:

  • Create "Finance Department" policy with export/scheduling
  • Create "General Departments" policy without these features
  • Assign appropriately
  • Contact team@dashboardfox.com about additional policies

Scenario: Testing New Features

Problem: You want to test new branding configuration before rolling out.

Solution with One Policy:

  1. Document your current configuration
  2. Assign policy to a small test group
  3. Make changes and test
  4. If issues arise, revert to documented configuration
  5. Once validated, assign to broader groups

Better Solution with Multiple Policies:

  • Keep existing policy in production
  • Create new "Beta" policy for testing
  • Assign to test group
  • Once validated, update production policy or switch users over

Scenario: Subsidiary or Division Branding

Problem: Your organization has multiple subsidiaries that need their own branding.

Solution:

  • License additional Application Branding policies (one per subsidiary)
  • Create Login Page Branding per domain if each has their own access URL
  • Configure colors, logos, and features per subsidiary
  • Contact team@dashboardfox.com about multiple policy licensing

Testing and Troubleshooting

Testing Checklist

Before rolling out new branding:

  • [ ] Test with a user in each affected group
  • [ ] Verify logout/login applies changes
  • [ ] Check embedded content if applicable
  • [ ] Test all custom links (Support, Documentation, Logo URL)
  • [ ] Verify logos display correctly at different screen sizes
  • [ ] Confirm colors are readable and accessible
  • [ ] Test any Custom JS for errors in browser console
  • [ ] Validate Custom CSS doesn't break layout

Common Issues and Fixes

Issue: Branding changes not appearing

  • Solution: Have users log out completely and log back in. Branding applies at login time.

Issue: Error "DashboardFox only allows one branding record"

  • Solution: You've reached your policy limit. Either disable/delete the existing policy, or contact team@dashboardfox.com about licensing additional policies.

Issue: Logo not displaying

  • Check: File format is JPG, PNG, or SVG (not WebP)
  • Check: URL is accessible if using linked images
  • Check: File size is reasonable for web display

Issue: Some users see old branding

  • Check: Policy is set to Active
  • Check: Users are assigned to the correct group
  • Check: Users have logged out and back in since changes

Issue: Custom CSS not working

  • Check: CSS syntax is valid
  • Check: Selectors are correct (use browser developer tools)
  • Check: No conflicting CSS elsewhere
  • Consider: Using !important flags for overrides

Issue: Features hidden but some users still need them

  • Solution with one policy: Use DashboardFox permissions to grant access to specific users even if hidden in UI
  • Better solution: License additional policies for different user tiers

Issue: Session timeouts showing login page in embeds

Performance Considerations

Logo File Sizes

Keep logo files reasonably sized (under 500KB) for fast loading. SVG is ideal for logos as it scales perfectly.

Custom JS

  • Test custom JavaScript thoroughly
  • Avoid heavy operations that slow page load
  • Use async loading for external scripts when possible

Custom CSS

  • Keep CSS efficient and targeted
  • Avoid overly broad selectors
  • Test across different browsers

Documentation for Your Team

When managing branding policies, maintain documentation:

For each policy, document:

  • Policy name and purpose
  • Which groups/users it applies to
  • Why specific features are enabled/disabled
  • Any custom code and its purpose
  • When it was created and by whom
  • Any special testing requirements

Template example:

Policy: Company-Wide Standard
Created: 2024-01-15
Created by: [Admin Name]
Assigned to: ALL USERS

Purpose: Consistent branding for all employees with balanced feature set

Features Enabled:
- Viewing and basic interaction features
- Export and print for all users
- Refresh and filtering capabilities
- Hide SQL view (security)
- Hide anonymous sharing (control distribution)

Embed Configuration:
- Simplified for department portals
- Hide editing features in embeds
- Keep viewing features enabled

Custom JS:
- Analytics tracking (Google Analytics)
- Session timeout redirect to intranet

Notes:
- Reviewed quarterly
- Finance requested export capability - enabled globally
- Next review: April 2024

Upgrading and Maintenance

When Adding New Features

As DashboardFox releases new features:

  1. Review your branding policy
  2. Decide if new features should be visible
  3. Update policy accordingly
  4. Test with representative users
  5. Communicate changes to affected users

Regular Policy Reviews

Schedule periodic reviews (quarterly or semi-annually):

  • Is the policy still aligned with organizational needs?
  • Have departments or roles changed?
  • Are there new use cases requiring different configurations?
  • Is documentation up to date?
  • Would additional policies improve the user experience?

Considering Additional Policies

Evaluate licensing additional policies if:

  • Different departments have conflicting feature requirements
  • External users need significantly different interface than internal
  • Testing and production environments need separation
  • Subsidiaries or divisions require their own branding
  • User feedback indicates current configuration doesn't meet diverse needs

Contact team@dashboardfox.com to discuss your requirements.

Advanced Techniques

Using Custom JS for Conditional Logic

You can add logic based on user attributes:

// Example: Show a notification for admin users
if (window.currentUser && window.currentUser.isAdmin) {
  // Add a custom notification
  document.addEventListener('DOMContentLoaded', function() {
    // Your custom code here
  });
}

Dynamic Branding Based on Date

Use Custom JS to change branding for special events:

// Example: Holiday branding
var today = new Date();
if (today.getMonth() === 11) { // December
  document.body.classList.add('holiday-theme');
}

Then use Custom CSS to style .holiday-theme.

Integrating with Your Intranet

Use Custom JS to communicate with parent windows when embedded:

// Post message to parent window when report loads
window.parent.postMessage({
  type: 'dashboardfox-report-loaded',
  reportId: window.currentReport.id
}, '*');

Your intranet can listen for these messages and react accordingly.

Making the Most of Limited Policies

If you're working within the default policy limits, these strategies maximize flexibility:

  1. Use DashboardFox Permissions Extensively - Control access through permissions rather than just branding
  2. Leverage Per-Item Settings - Customize individual dashboards and reports beyond the global policy
  3. Differentiate Embed vs. Full App - Create simplified embedded experiences even with one policy
  4. Use Folders Strategically - Organize content so different groups see different dashboards
  5. Consider Guest Access - Use guest/anonymous sharing for external users instead of authenticated access

When these strategies aren't enough, contact team@dashboardfox.com about licensing additional policies.

Getting Help

If you're stuck with a branding scenario:

  1. Check the specific articles for detailed configuration steps
  2. Review this best practices guide for similar scenarios
  3. Test with a single user before rolling out broadly
  4. Contact team@dashboardfox.com for support or to discuss additional policy licensing

Key Takeaway: DashboardFox's branding capabilities provide the flexibility to create professional, customized experiences. With the default single policy, focus on serving your primary use case well and use permissions and per-item settings for exceptions. When you need more segmentation, additional policies are available through licensing.

Questions about licensing additional policies? Contact team@dashboardfox.com

Related Articles