Expensify Okta Integration

Priya2021 Expensify Customer Posts: 7 Expensify Newcomer

The document for enabling deactivation in expensify via okta states that First Name and Last Name attribute in okta should be made not required (step 9 -11).

Can i please know why is this required as we have made these attributes mandatory for user creation in okta.


  • Priya2021
    Priya2021 Expensify Customer Posts: 7 Expensify Newcomer
  • iOINADOINwoinadf
    iOINADOINwoinadf Expensify Customer Posts: 2 Expensify Newcomer

    It would be great if the Okta integration could be expanded. We use Okta as the intermediary between our HRIS system and all downstream services/applications. The reason for this is if we ever decide to switch our HRIS system, that data will be retained towards Okta.

    When it comes to account provisioning or deactivation, currently the only way to deactivate a user is by forcibly closing & deleting all accounts in question, rather than just actually deactivating (rendering the user unable to login).

    Okta does creation and provisioning as well, and this could be accomplished via location specific apps within Okta, or a single application in Okta where then the app (EG: Expensify) can integrate policies based on location.

    Would really like to see the Okta integration improved.