In response to customer feedback, Filevine will be making changes to the Filevine developer portal.
Currently, API keys are associated with individual Filevine users. Each user can log in and create an API key that can automate their user’s actions in Filevine. However, our customers have found it difficult to manage API dummy users and permissions for third party help.
In response to these challenges, the Filevine Portal is being restructured in two key ways:
- First, the portal’s organization will now revolve around Orgs rather than individual users. “Portal Admins” will be able to grant or deny Portal Org access to anyone, including third parties without Filevine accounts. All keys will be accessible to those with Portal Org access. All users who have been granted portal access before this change will be granted Portal Admin status.
In order to facilitate this change, the authentication for the Filevine Portal users needed to be uncoupled from Filevine. Consequently, users will no longer log into the Filevine Portal using Filevine credentials. All current Portal Users users will be receiving a temporary password via email. Upon first login, users will be prompted to create a new password and set up two-factor authentication. If you do not receive a temporary password, please whitelist email@example.com and then reset your password from the portal website to get a password reset code.
- Second, each Portal Org will now come with an API user that is created and added automatically to your Filevine Org as an org administrator. Going forward, all API keys created in the portal will be associated with this API user rather than a Filevine user. Keys that were generated previously will continue to function.
Thank you for your feedback. If you have further questions or concerns, please email us at firstname.lastname@example.org.