iAMT scope and responsibilities
Categories and best practices
Identity Management system
Tier 2 support structure
SSO and PIV exemption processes
Viewing and managing user permissions
Reactivation procedures and requirements
iAMT (iFAMS Access Management Team) manages iFAMS and Power BI access related to iFAMS exclusively.
For requests outside our scope, redirect to appropriate teams with proper contact information.
Not managed by our service desk or provisioned through IAM.
Frequently confused with iFAMS due to similar labeling.
Completely separate system from iFAMS.
Users without iFAMS/Power BI access
Updates to existing accounts & roles
Remove access in iFAMS
Reactivate user access
Thorough documentation helps iAMT CSRs research efficiently and reduces back-and-forth communication.
IAM (Identity Management Toolkit version 3.1.3.5 [1.5] IAM Provisioning Blue) is the primary tool used to provision users for access in iFAMS.
Research is conducted using the User Directory in IAM
Use the drop-down menu to select iFAMS to filter out other unsupported applications.
No iFAMS access yet
Check Account History
Access being removed
Once provisioned, everything in IAM will show under: System Administrator > Security > Principals in iFAMS
ASOS functions as Tier 2 in the iFAMS Service Desk roles and responsibilities.
Provides mid-level technical support for iFAMS customer inquiries about user access management and reference table maintenance.
Works with and supports the Access Management team to ensure user access aligns with regulations and people are activated promptly.
Runs reports to ensure separation of duties requirements are enforced and customer access is accurately reflected in IAM.
Handles all provisioning in IAM, including updates when new security organizations are added or existing users require adjustments.
iFAMS requires Single Sign-On (SSO) access.
What is a PIV Exemption? Granted by IT for users unable to use a PIV badge.
System Administration > Security > Principals
View iFAMS access details for specific users. Initial screen displays Active/Inactive Status.
Requests are routed to the iAMT CRM Workbasket: iFAMS@Station
Critical: Once reactivated, the user must log into iFAMS the same day to prevent the system from marking the account inactive again overnight.
If user is Inactive and requesting reactivation:
To avoid future deactivation, users should:
Important: Users who have not logged into iFAMS for 90 days will be deactivated and will need to enter a ticket via the iFAMS Customer Self Service Portal to be reactivated.