---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Assign users to Scan Engine groups

# Assign users to Platform Health groups {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

In addition to assigning Impact users to groups, Platform Health users must also be part of a group for the Scan Engine feature.

## Before you begin

Feature allocation and availability in the Platform Health Scan Engine is based on role and group assignment. See [Track Platform Health trends](https://servicenow-prod.fluidtopics.net/QXHio4M3Y73q~gjnPRrWQg "Analytics Dashboards provide a graphical way to view detailed information relating to findings, both pending and resolved, with the Scan Engine. The dashboards are role-based, allowing for persona-based views of information. They display  key metrics,  charts, and  trend analysis.") for additional information on role-based feature availability.  
Note:  
You may return to the various steps in the configuration if you don't complete the entire setup at once. As you complete each step successfully, mark the step as complete. Subsequent tasks are locked until the previous step is completed.

Role required: impact app admin or admin

## Procedure

1. [Use Guided Setup to onboard users to the Impact Store Application](https://servicenow-prod.fluidtopics.net/k_SJQbevUaFUGXCBnzHjGg "Onboard new and existing users to the Impact Store Application.").
2. Navigate to AllImpactGuided SetupAssign Platform Health users.
3. Select a user group to assign users to a group.
4. Create Development Teams.  
   Development teams are necessary so each persona can access the relevant Platform Health dashboard. Each record indicates a team and a development team lead that Scan Engine findings will be reported on the Analytics Dashboard.
   1. Navigate to AllImpactConfigurationScan Engine Properties.
   2. In the Team Leads related list, select New.
   3. Create the relevant development teams assigned to the appropriate team lead.  
      See [Configure scanning properties per persona](https://servicenow-prod.fluidtopics.net/SCRT~mW6b_P32mcWo~d~HQ#teamdev-scanning-properties "You can view and configure a variety of information, formatted into lists, that the Scan Engine uses to permit users, team leads, and admins to access content.") for additional information on assigning team leads to development teams.
5. Select Mark as Complete to enable the next configuration step.
{#assign-users-scan-engine-groups__steps_r5x_5mq_lgc}

## What to do next

[Activate Scan Engine and review settings](https://servicenow-prod.fluidtopics.net/gHOdzFEvUGTYdPdLeIgHFw "Use Impact Guided Setup to set up the minimum required configuration options in order to run the first system scan.")

*[\>]: and then


