Provisioning App Users

Provisioning POM Safe Enterprise App Users

Overview

Each account created through the POM Safe Enterprise app consumes one available license from your organization's subscription. Organizations can choose between two access management methods to control how users provision their accounts and consume licenses.

Access Management Methods

Organization-wide Invite Code

The Organization-wide Invite Code is a 6-digit code unique to your organization, provided by POM. Any individual with access to this code can create an account in the POM Safe Enterprise app and consume a license.

How it works:

• Share the 6-digit invite code with your end-users
• Users enter the code during account creation in the mobile app
• Accounts are created immediately without pre-authorization

Advantages:

• Simplified onboarding: Users do not need to be preloaded into the Safety Hub before creating their accounts
• User autonomy: End-users can self-provision their accounts without waiting for administrator action
• Faster deployment: Ideal for rapid rollouts where pre-registration isn't feasible

Limitations:

• Reduced visibility: Leadership has limited ability to track which users have completed onboarding
• Manual administration: Group and Team assignments must be configured manually through the Safety Hub after account creation
• Less license control: Without pre-authorization, tracking and controlling license consumption is more challenging

Best for: Organizations prioritizing speed of deployment and user convenience over administrative oversight.

---

Unique Identifier Method (Recommended)

The Unique Identifier method requires users to enter a specific piece of identifying information during account creation. Only users who have been preloaded into the Safety Hub with matching identifiers can successfully create accounts and consume licenses.

Supported identifier types:

• Mobile phone number
• Email address
• Employee ID

How it works:

• Upload user information to the Safety Hub via CSV file before deployment
• Users enter their unique identifier during account creation in the mobile app
• The system validates the identifier against the Safety Hub database before allowing account creation

Advantages:

• Enhanced visibility: Track onboarding progress and identify which users have not yet registered
• Automated assignments: Groups and Teams can be assigned automatically when included in the CSV upload file
• License control: Only pre-authorized users can consume licenses, preventing unauthorized access
• Improved reporting: Multiple identification methods provide more robust search filters and reporting capabilities within the Safety Hub

Limitations:

• Upfront preparation: Requires users to be preloaded into the Safety Hub before they can register in the app
• Additional administration: Initial CSV file preparation and upload required before deployment

Best for: Organizations requiring administrative oversight, structured onboarding tracking, and granular control over license allocation.

---

Recommendation

The Unique Identifier method is recommended for most organizations due to its superior visibility, control, and automation capabilities. While it requires upfront preparation, the benefits of tracking onboarding progress, automatic group assignments, and controlled license consumption typically outweigh the initial administrative investment.

Organizations should select the Organization-wide Invite Code method only when rapid deployment is critical and administrative oversight is less of a priority.

---

Next Steps

• Determine which access management method aligns with your organization's needs
• For Unique Identifier implementation, prepare your user CSV file with the appropriate identifier fields
• Contact your POM representative if you need assistance selecting or implementing your chosen method