How to Map SaaS Applications to Departments for Clearer Visibility. If you’re trying to control SaaS spend, reduce shadow IT, or tighten compliance, you need context. Specifically: which department is using what, how often, and why. In this video, we'll walk through a practical process for mapping SaaS applications to departments, improving visibility, strengthening governance, and reporting meaningful insights to clients. Before we begin, be sure to subscribe to NinjaOne’s IT video hub and our YouTube channel for more tech content like this. Step-by-Step SaaS Mapping for MSPs. Step 1: Collect SaaS Usage Data From the Identity Provider. First, open the client’s IdP admin portal and export SSO/app usage logs. Make sure to export the following: App name, User identity, Login frequency, Last login timestamp, License status or activity flags Export to a structured format like CSV, an API feed, or a direct connector. Step 2: Map Users to Departments. Next, follow these steps to map users to their respective departments: Pull department attributes from HRIS platforms, payroll systems, Active Directory attributes, or AD group tags. Join department data to your IdP usage logs using a common identifier such as: Email, UPN, or employee ID (if standardized) Enrich each SaaS activity record so every login event can be attributed to a department. Once you do this, shadow IT detection and cost attribution become much easier. Step 3: Aggregate Usage by App and Department. Now that each record has department context, you can build department-level SaaS visibility. Group usage data by app and department. Calculate operational metrics such as: Active users per department Last login timestamp, License count vs. active usage Create a table or dashboard that's easy to review during QBRs and operational reviews. Step 4: Visualize and Share Findings. Build a dashboard in Excel, Power BI, or a PSA-integrated reporting platform. Make sure to include the following KPIs: App usage by department Cost attribution by team, Redundant apps and overlap Login frequency and license utilization Adoption trends over time Use the same dashboard format every review cycle so clients recognize trends immediately. Present these insights during QBRs or regular leadership reviews to help clients understand SaaS adoption, costs, and optimization opportunities. Step 5: Identify Shadow IT and Risky Applications. Department mapping helps prevent the classic scenario where IT blocks a tool without realizing one team is using it for a critical workflow. First, compare your discovered application list to the client’s approved SaaS catalog. Highlight applications that are not approved, show significant usage, or are accessed by sensitive departments. Build a remediation plan for each app, whether that means officially adopting it, restricting access, or educating users on approved alternatives. Lastly, escalate risky findings to security/compliance stakeholders. Step 6: Automate Mapping Updates. Manually mapping SaaS usage becomes difficult to scale as environments grow and users move between departments. A lightweight option is to refresh usage logs on a schedule and enrich them with AD department data. Here’s a short example PowerShell snippet: For a production-ready version, including safer identity lookups, error handling, and scheduled execution, use the full workflow in the blog. Step 7: Embed Reports Into Client Reviews. The final step is making SaaS governance part of the client's regular business review process. This means including SaaS-to-department reporting in QBRs or monthly operational reviews. Highlight the following: Top apps by department, Redundant tool overlap across teams Shadow IT and risky apps, Underused licenses approaching renewal Department-specific security gaps Provide clients with clear recommendations, such as consolidating tooling or retiring unused applications. Mapping SaaS applications to departments is one of the fastest ways to turn SaaS sprawl into governable infrastructure. For more information, check out our official blog post on how to map SaaS applications to departments for clearer visibility, linked in the description below.