VTS works with partners across the industry to help customers and their users get the most out of the platform. We'll take a a look at the types of integrations you can explore—you can check out other guides in this section for specific integrations. 

Just remember that systems and workflows can be more complex in different contexts. Reach out to your partner at VTS to connect on finding the best solutions.

1. External links
2. Embedded views
3. Embedded views with authentication
4. APIs
5. Hybrid integration

External links

The most basic option is a link. When you want someone to navigate somewhere other than Activate, you can use an external link to open in a new browser or direct people to a mobile app. There aren't any technical requirements and it's pretty easy to set up. It's a good option for simply getting from point A to point B.

Embedded views

An embedded view lets users navigate another application right from within the Activate platform. To set up an embedded view, the partner app has to have a web interface—basically, it has to be viewable in a web browser. It's a better experience if it has adaptive mobile design, too.

Once you're set up, it takes almost no maintenance to give your users a seamless in-app experience with whatever the partner app has to offer.

Embedded views with authentication

This is just like an embedded view, but it adds an authentication process. You can leverage Activate's authentication to log the user into the partner app—Activate acts as the authentication provider and validates the user across the two platforms.

Adding authentication gives the best, frictionless experience. People won't be asked to login if they access the partner app through Activate.

APIs

You can create custom workflows using the Activate API, typically by pushing data (like user or building information) to Activate or by retrieving the same kind of data from the platform. The requirements depend on what you'd like to see out of the integration, so reach out if you want to see what's possible. 

Hybrid integration

You can even combine an authenticated, embedded experience with an API. These are usually the most context-dependent of all, so reach out any time if you want to talk particulars.