Asset 360 Mobile > Asset 360 in Field Service Mobile App > Admin Configurations > Configuring Asset 360 Mobile with Managed Components
Configuring Asset 360 Mobile with Managed Components
Asset 360 features are available for the SFS mobile application through the ServiceMax Asset 360 managed package. You do not need an unmanaged extension package to leverage Asset 360 in the SFS mobile application. You must perform the following steps to enable Asset 360 features for the SFS mobile app users through the managed components.
1. Install the ServiceMax Asset 360 managed package. To know more, refer to Install Package.
2. On Work Order and Asset objects where the LWC is configured as quick action, switch the references from un-managed components to managed components for the following capabilities.
Asset Hierarchy
Asset Timeline
Service Coverage
Asset Technical Attributes
* 
NOTE:
The packaged components begins with SVMXA360:svmxMob. For example, for the Asset Timeline LWC, the component name is SVMXA360:svmxMobAssetTimeline. To configure all Asset 360 managed mobile components, refer to Create LWC Quick Action.
You must add feature-specific permission set to the objects.
3. Configure the Field Service Mobile permission set and assign it to the user profiles in addition to the Asset 360 Core permission set. To know more, refer to Configure Mobile Permission Set.
4. Enable the Lightning Web Security option in the org. You can enable it by navigating to Setup > Security > Session Settings > Use Lightning Web Security for Lightning Web Components and Aura Components.
5. To enable SPM Wizard in the required object, configure the SPM Wizard component as quick action, and then assign it to the page layout. To know more, refer to Configure SPM Wizard.
* 
NOTE:
You must assign the user or profile to the A360 Mobile Configuration Access record.
Both web and mobile components refer to the same admin setup configurations.
If you have already configured the un-managed mobile components before the A360 10.0 release, both un-managed and managed components can appear in the same org for the same components. To use the managed components only, you must delete the un-managed components and configurations manually.
Was this helpful?