The new App Integrations page in Clio Manage features applications built by Clio as well as third-party applications built by the Clio app developer community.
NOTE: In order to have your app featured on the App Integrations experience, your app must be integrated with Clio Identity and you must support SSO (single sign-on) with Clio. Please reach out to us at email@example.com with the required information outlined in this article to get started, with your application's name in the subject line.
What are the benefits of featuring my app within Clio Manage?
Because the App Integrations page is embedded directly within Clio Manage, Clio customers will no longer be redirected to the external Clio App Directory site to discover available integrations. Instead, Clio customers can now add integrations at the click of a button without ever leaving Clio Manage, making it easier than ever before for Clio users to find your app, understand what they can use it for, understand how much it costs, and install it for their Clio account.
myFirmData, a Clio third-party integration, as featured on the App Integrations experience.
How do Clio users add applications to Clio Manage via the App Integrations page?
When a user clicks the Add to Clio button for an application on the App Integrations page, a new browser window is opened, which will point to the Add to Clio URL of your application.
A new browser window with your application’s login page appears after clicking the Add to Clio button.
It is recommended that your application’s content is responsive and functional in this smaller, fixed-width browser window. We also recommend refraining from displaying any additional irrelevant links (marketing links, other external resources, etc.) that might divert the user from the authentication flow within this window.
It is required that upon a user’s successful completion of this authentication flow, you redirect the user to a callback page on Clio Manage (not your application’s dashboard page). The callback page URL is as follows:
Landing on this callback page will ensure that the new browser window which was opened at the start of this flow will close and refresh the state of the user’s App Integrations page with updated information.
Adhering to these requirements ensures that the Clio Manage user experience remains seamless, while also allowing Clio Manage to accurately provide feedback to the user that they have successfully integrated with your application, and that they may now log in to and access your application anytime instantly using SSO via their App Integrations page.
How do Clio users access their integrated applications via the App Integrations page?
Once a user has successfully integrated your application with their Clio account, your application will appear under the user’s My Integrations tab within their App Integrations page. From here, the user can open your application or revoke your application’s access to their Clio account as they please.
After integrating with your application, the user can now open your application directly from Clio Manage.
When a user clicks the Open app button, your application’s App URL will be loaded in a new browser tab. As the user has already been authenticated during the initial process of integrating with your application, the user should be seamlessly redirected. If the user’s login session on your application has expired, your application should gracefully redirect them to the appropriate page where the user can sign in via SSO using their Clio account credentials again.
How can I have my app listed on the App Integrations page?
Apps listed on the Clio App Directory can also be listed on the App Integrations page, provided the following:
- The app is already listed on the Clio App Directory or has provided the information required for launching your app in the Clio App Directory
- The app is integrated with Clio Identity for authentication and has implemented SSO (single sign-on) with Clio
In addition to the requirements outlined for launching your app in the Clio App Directory, ensure you have the following pieces of information ready before reaching out to us at firstname.lastname@example.org to have your app listed on the App Integrations experience:
|Add to Clio URL||A custom URL that authenticates a Clio user and adds the application to Clio Manage. Refer to our article on Integrating with Clio Identity for additional details.|
|A URL to your application's homepage or dashboard that users are redirected upon successfully logging in.|
|Marketing URL||A URL to your application's general public-facing marketing website.|
|Pricing URL||A URL to the pricing page of your application's general public-facing marketing website.|
In order to register your application on the Clio Identity service, we need to know a list of redirect URIs you will be using for your authorization flow. The list should include your development and production redirect URIs.
|Developer GitHub Handles||For your convenience, we have a GitHub repository with a sample implementation demonstrating how to integrate with Clio Identity and allow Clio users to SSO into an application. Any developers that would like to see this example will need to send us their GitHub account handles so that access can be granted. The application is built using Ruby on Rails, but the general workflow is extendable to your framework of choice.|
We’re currently using the Clio Manage API for authentication. Will that be discontinued?
No. All Clio Manage API behavior will stay as is. The Clio Manage API still continues to provide authorization for accessing all resources through OAuth 2.0. However, we highly recommend integrating with Clio Identity for authentication purposes, as it is also a prerequisite to having your app listed on the App Integrations experience.