Start a project
Menu
ServicesAll servicesCybersecurityCloud EngineeringApplication ServicesEnterprise PlatformsData & AnalyticsAI & Machine LearningInternet of ThingsMobilize Talent
PlatformsAll platformsIdentity and accessPrivileged access and secretsERP, HCM and financeCRM, ITSM and automationHealthcareInsurance and bankingData and integrationCloud and AIIndustrial, utilities and mainframeSkills matrix
Case studiesAll case studiesIdentity and accessPrivileged accessSecurity operationsCloud and infrastructureApplicationsERP and HCMCRM, ITSM and automationIndustry platformsData and analyticsAI and agents
IndustriesAll industriesEnergy, oil & gasHealthcare payersBanking & financial servicesInsurancePublic sectorManufacturingLocations
InsightsField notesLearning tracks
CompanyAbout CohashPortfolioSkills matrixCareersTrust and securityContact
Start a project
enterprise platforms · business intelligence

Reports inside the CRM, showing only what that user is allowed to see.

A sales manager shouldn't need to open a second tool to see pipeline, and a service rep shouldn't see accounts outside their region. We build reporting inside Salesforce, Dynamics 365 and ERP screens, with row-level security that follows the app's own permissions.

Talk to an engineerSee the architecture
platforms
enterprise-platforms / business-intelligence 4 platforms
01 · APP DATA 02 · SECURITY MAPPING 03 · EMBEDDED BI 04 · USERS Salesforce objects: opportunities · cases Salesforce objects opportunities · cases Dataverse: Dynamics 365 · Power Apps Dataverse Dynamics 365 · PowerApps ERP companies: orders · approvals ERP companies orders · approvals Row-level security: roles · business units · companies Row-level security roles · business units· companies Salesforce reports and Tableau: dashboards on Lightning pages Salesforce reportsand Tableau dashboards onLightning pages Embedded Power BI: model-driven apps · forms Embedded Power BI model-driven apps ·forms Sales and service teams: pipeline · backlog · order status Sales and serviceteams pipeline · backlog ·order status
SalesforceMicrosoft Dynamics 365Microsoft Power PlatformMicrosoft Fabric
in short·15-second read

Platform-embedded business intelligence puts reports and dashboards inside the applications people work in, such as Salesforce, Dynamics 365 and ERP.

Cohash builds Salesforce reports and Tableau dashboards, embeds Power BI in Dynamics 365 and Power Apps, and designs row-level security so each user sees the same records in a report that they can see in the app.

you probably need this if
  • Sales managers export Salesforce reports to Excel to see the numbers they need.
  • A Power BI report embedded in Dynamics 365 shows records the user can't open in the app.
  • Hundreds of dashboards exist and nobody knows which ones are still used.
Ask an engineer facts checked 2026-10-20 · 1 source
how it runs
  1. 01Inventory
  2. 02Design
  3. 03Build
  4. 04Retire and hand over
you keep
  • Report inventory with usage and owners
  • Metric definitions for operational reports
  • Security mapping between app permissions and BI
+ 2 more documents
who does it
Power BI developerSalesforce CRM Analytics developerDynamics 365 reporting developer Microsoft Certified: Power BI Data Analyst Associate
platforms
proof
2 case studies on this
the story · business intelligence

From the first call to a setup your own team can run.

Here's what usually prompts a call about your Business Intelligence, what we do about it and in which order, and where you end up.

  1. chapter 01 · where it hurts

    Why teams reach out

    • Sales managers export Salesforce reports to Excel to see the numbers they need.
    • A Power BI report embedded in Dynamics 365 shows records the user can't open in the app.
    • Hundreds of dashboards exist and nobody knows which ones are still used.
  2. chapter 02 · what we change

    How we solve it

    • Salesforce reports and dashboards
    • Power BI in Dynamics 365 and Power Apps
    • Security that matches the app
    • Operational metrics
    • When to move to the warehouse
  3. chapter 03 · how it runs

    Our approach

    • Inventory
    • Design
    • Build
    • Retire and hand over
  4. chapter 04 · where you end up

    What changes

    • Each seller sees the same accounts in the report as in the app.
    • Managers find one dashboard per role with numbers they trust, and the export habit loses its reason to exist.
    • Report inventory with usage and owners
    • Metric definitions for operational reports
what we do

Where we spend the hours

5 areas of work, each one done by an engineer who has run it in production.

  1. Report types, dashboards and Tableau views built on objects your teams already maintain, with fields and filters cleaned up first.

  2. We embed Power BI in model-driven apps and forms, with Dataverse as the source and filters passed from whatever record the user has open.

  3. Row-level security in Power BI or Tableau mapped to Salesforce roles, Dataverse business units or ERP companies. Then we test it with real users.

  4. We define pipeline, case backlog, order status and approval queues with the people who act on them, and stick to the handful of numbers they check every day.

  5. If a report needs data from three systems, put it on the warehouse. We decide which reports cross that line and move them to analytics BI.

capability 01 / 05in production

Salesforce reports and dashboards

Report types, dashboards and Tableau views built on objects your teams already maintain, with fields and filters cleaned up first.

talk to an engineer about this →
capability 02 / 05in production

Power BI in Dynamics 365 and Power Apps

We embed Power BI in model-driven apps and forms, with Dataverse as the source and filters passed from whatever record the user has open.

talk to an engineer about this →
capability 03 / 05in production

Security that matches the app

Row-level security in Power BI or Tableau mapped to Salesforce roles, Dataverse business units or ERP companies. Then we test it with real users.

talk to an engineer about this →
capability 04 / 05in production

Operational metrics

We define pipeline, case backlog, order status and approval queues with the people who act on them, and stick to the handful of numbers they check every day.

talk to an engineer about this →
capability 05 / 05in production

When to move to the warehouse

If a report needs data from three systems, put it on the warehouse. We decide which reports cross that line and move them to analytics BI.

talk to an engineer about this →
typical situations

Situations we walk into

We pieced these together from Business Intelligence situations that come up a lot. They're patterns. You won't find a specific client in them.

case file 01

Embedded Power BI that shows every region's pipeline

composite · not a client story
  1. Beforethe situation

    Each seller can open only their own region's accounts in the app. Open the Dynamics 365 account form, though, and the Power BI report there shows pipeline for every region. The dataset is an import model refreshed by a service account.

  2. What we dothe work

    Map Dataverse business units to Power BI row-level security roles, or switch to DirectQuery against Dataverse where volumes allow so the user's own permissions apply. Test with a persona from each region and compare what the report shows with what the app shows.

  3. Afterwhere you end up

    Each seller sees the same accounts in the report as in the app. The persona tests run again whenever security roles change.

case file 02

Hundreds of Salesforce dashboards and managers still exporting to Excel

composite · not a client story
  1. Beforethe situation

    The Salesforce org has hundreds of reports and dashboards, plenty of them in private folders belonging to people who left. Managers export to Excel because they can't tell which dashboard to trust.

  2. What we dothe work

    We pull last-run dates from report metadata, warn owners and archive what hasn't run for months. Then a short set of dashboards per role gets rebuilt on agreed definitions, in shared folders with named owners.

  3. Afterwhere you end up

    Managers find one dashboard per role with numbers they trust, and the export habit loses its reason to exist.

case studies

Business Intelligence case studies

All case studies
migration Data and analytics

Power BI Premium P SKUs to Microsoft Fabric F SKUs

Moving Power BI Premium per-capacity P SKUs to Microsoft Fabric F SKUs before the agreement ends, sized from real load and reassigned in validated batches.

read the case study
migration Data and analytics

Tableau to Power BI

Moving Tableau workbooks to Power BI semantic models, scoped by what people open, with row-level security and numbers that match before anyone switches.

read the case study
upgrade Industry platforms

Nasdaq Calypso upgrade to V19

Upgrading Nasdaq Calypso to V19, with server consolidation, properties moved to the database, the WebUI and deployment changes tested on your own trades.

read the case study
migration Industry platforms

Duck Creek on-premises to Duck Creek OnDemand

We move self-hosted Duck Creek Policy, Billing and Claims onto Duck Creek OnDemand and keep the product and rating content, integrations and data intact.

read the case study
migration ERP and HCM

Dynamics AX 2012 to Dynamics 365 Finance & Operations

We take AX 2012 R2 or R3 systems to Dynamics 365 finance and operations apps, and the code, data, attachments and integrations come across with them.

read the case study
migration CRM, ITSM and automation

Dynamics CRM on-premises to Dynamics 365 online

We move Dynamics CRM or Customer Engagement 9.x off your servers and onto Dynamics 365 online, rebuilding customizations, reports, integrations and sign-in.

read the case study
architecture

How embedded reports inherit the app's own permissions

Reports and dashboards run inside Salesforce, Dynamics 365 and ERP screens, reading the app's own data. Row-level security in Power BI or Tableau is mapped to the app's roles, so a user sees the same records in a report as in the app.

How embedded reports inherit the app's own permissions Reports and dashboards run inside Salesforce, Dynamics 365 and ERP screens, reading the app's own data. Row-level security in Power BI or Tableau is mapped to the app's roles, so a user sees the same records in a report as in the app. 01 · APP DATA 02 · SECURITY MAPPING 03 · EMBEDDED BI 04 · USERS role hierarchy security roles company access filtered rows filtered rows in-app dashboards record context Sf Salesforce objects opportunities ·cases D365 Dataverse Dynamics 365 · PowerApps ERP companies orders · approvals Row-level security roles · business units ·companies Salesforce reports andTableau dashboards on Lightningpages PP Embedded Power BI model-driven apps ·forms Sales and service teams pipeline · backlog · orderstatus
Read the diagram as text
  1. Salesforce objects → Row-level security: role hierarchy
  2. Dataverse → Row-level security: security roles
  3. ERP companies → Row-level security: company access
  4. Row-level security → Salesforce reports and Tableau: filtered rows
  5. Row-level security → Embedded Power BI: filtered rows
  6. Salesforce reports and Tableau → Sales and service teams: in-app dashboards
  7. Embedded Power BI → Sales and service teams: record context
how it runs

A typical engagement

We don't start a step until the last one has produced something you can check.

  1. step 01

    Inventory

    Existing reports, dashboards and the decisions they support catalogued, with usage data where the platform provides it.

  2. step 02

    Design

    We agree metric definitions, security mapping and where each report sits in the app with the teams who'll use it.

  3. step 03

    Build

    Reports built and embedded, then tested with user personas for both numbers and access.

  4. step 04

    Retire and hand over

    Unused reports archived and admins trained to maintain the rest.

you keep

What you're left with

We write these for your Business Intelligence setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.

  • inventory01

    Report inventory with usage and owners

    yours to keep
  • report02

    Metric definitions for operational reports

    yours to keep
  • inventory03

    Security mapping between app permissions and BI

    yours to keep
  • report04

    Embedded reports and dashboards

    yours to keep
  • report05

    Admin guide for report maintenance

    yours to keep
platforms

Tools we work in

SalesforceCRMMicrosoft Dynamics 365CRM & ERPMicrosoft Power PlatformLow-code & automationMicrosoft FabricData platform
talent and delivery · business intelligence

Certified engineers, wherever you need them.

Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.

Onsite

Engineers at your sites in the US

Nearshore

Overlapping hours with US teams

Offshore

Overnight progress on your backlog

All time zones

Coverage handed over across time zones

24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
certifications our engineers hold
roles we staff
  • Power BI developer
  • Salesforce CRM Analytics developer
  • Dynamics 365 reporting developer
  • Fabric engineer
  • BI administrator
due diligence · business intelligence

Questions to ask any partner, including us.

Put these to anyone bidding on your Business Intelligence work. The ones who've done it answer differently from the ones who've read about it.

  1. Q1

    How will report security match what each user can see in the app?

    Embedded reports often run on a service account with broad access. Row-level security mapped to app roles and tested with personas is what stops a report leaking records.

  2. Q2

    Which reports belong inside the app, and which belong on the warehouse?

    Reports that join three systems or need long history strain in-app tools. Drawing that line early avoids building the same report twice.

  3. Q3

    What Power BI licensing do our viewer count and embedding method need?

    Microsoft is retiring Power BI Premium P SKUs in favor of Fabric F SKUs. Count your viewers and look at how reports are embedded. Those two answers decide between Pro, Premium Per User and capacity.

  4. Q4

    How will you decide which existing reports to retire?

    Usage data beats opinion. Last-run dates plus owner confirmation make a retirement list that nobody has to argue about.

01How is this different from your data and analytics BI work?

This page covers reporting inside a single platform, for the people who work in it. If you need data joined across systems, history the app doesn't keep, or a governed semantic layer, we build that on the warehouse. That's our data and analytics BI service.

02Do we need Power BI Premium to embed reports in Dynamics 365?

Licensing depends on who views the reports and how they are embedded. Microsoft is retiring Power BI Premium per-capacity P SKUs in favor of Fabric F SKUs, while Pro and Premium Per User licenses continue. We check your viewer count and embedding method before recommending a license.

03Can Salesforce users see Tableau dashboards without a separate login?

Usually yes, with single sign-on through your identity provider and embedding in Lightning pages. Access to the underlying data still depends on Tableau permissions, which we map to Salesforce roles.

04Can you move our Salesforce reports to Tableau or Power BI?

Yes, when they've outgrown what Salesforce reporting does well. We rebuild them with the same metric definitions and security, then retire the originals so two versions don't compete.

05How do you keep report numbers consistent across teams?

We write metric definitions down with the people who use them, name an owner for each, and build reports from those definitions. When two teams genuinely need different numbers, we give them different names instead of letting one label mean two things.

related

Often paired with

Projects on Business Intelligence usually end up touching one of these, so they're worth a look.

you are hereBusiness Intelligence
sources 1 source linked last checked 2026-10-20 content fingerprint e8ad65e2
  1. 01Microsoft Learn: Power BI Premium to Microsoft Fabric migration overviewlearn.microsoft.com ↗
Reviewed by the Cohash team Product names are trademarks of their owners. how we handle facts and data →
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

Book a working session See the case studies
useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it