Steps for Onboarding a new PACS user or integration partner

Glossary:

• PACS-USER – a user from a PACS partner
• OEM-INT – an Allegion employee on the OEM-Integration team 
• SW.SUPPORT – an Allegion employee from the Software Engineering team supporting Mobile Credentials.
• SPB – an Allegion employee from the go to market team that interacts with PACS-USERs.
  
  

Workflow:

1. PACS-USER creates account in Developer Portal (directed by SPB or OEM-INT)
   
   
2. PACS-USER sends requests to OEM-INT team to get access to Mobile Credential API & SDK
   1. OEM-INT team verifies PACS-USER has access to Mobile Credentialing documentation and has met Pre-Requisites.
      • If pre-requisites are not met, OEM-INT works with PACS-USER to meet requirements or this process ends.
   2. OEM-INT team works with PACS-USER to determine:
      • Username(s) or email(s) for Developer Portal  (usually one per developer)
      • Username(s) or email(s) for GitHub (usually one per developer)
      • Single Name for the Integration (company name is good)
      • Single Login email used for their site admin in ENGAGE
      • Single set of Public Keys needed for Integration Id
      • TenantId: Custom or Default Allegion
      • BitFormat:  RawData, 48X, etc.

1. OEM-INT sends email to SW.SUPPORT (software.support@allegion.com) with content from 2.b above.
   
   
2. SW.SUPPORT provisions the following for PACS-USER(s)
   • Within 3 business days - Subscriptions to Mobile Credential in Developer Portal
     • This includes enabling their ENGAGE site admin to create Credentials within the Mobile Credentialing API
               
   • Within 3 business days - Access to Private GitHub
   • Within 5 business days - Integration Id
3. SW.SUPPORT provides Integration Id to OEM-INT within 5 business days.
       
4. OEM-INT provides Integration Id to PACS-USER