What Do You Mean When You Say Integration?

In the world of web development, this is the most common reference to the term integration. On the most basic level, SSO is when your association management system (AMS) – like Re:Members– is bridged with your content management system (CMS) to create a seamless login experience for members.

There is nothing worse than requiring a member to login more than once on your website as they navigate across different third-party platforms. With SSO, there is a coded connection between your systems that allows a member to login once and then navigate from your web pages to your AMS pages and then back again without any interruption. In addition, other third-party platforms like job boards, learning management systems (LMS) or online communities can be linked into the SSO code so that you can create one large ecosystem of web-based tools for your members – all accessible to them through one login.

Very commonly coupled with SSO, design integration allows the visual user experience (UX) to be seamless as well. Your website’s branded design template (header, footer and sidebars) can be implemented into your third-party system (AMS, LMS and others) to create the visual impression that all your systems are actually one big system. This is a big plus in the user-friendliness column. Note, however, that some third-party systems, like online communities, sometimes prefer the user to see a unique visual experience across their application so the user can feel comfortable they are in the right place for peer-to-peer networking. For the most part, though, continuity in design between systems is desired.

Beyond SSO there is another scenario when integration between systems can be very useful. There may be information in your AMS that you’d like presented on your website in a unique and customized way. As a simple example, maybe you’d like committee and board members’ information pulled from the AMS and displayed on a web page.

One way to achieve this is by exporting the data from the AMS and housing it on a server. This data would represent the latest committee and board member information as of that moment in time. Then nightly (or more or less often depending on your needs) a snapshot of that data would be uploaded to the content management system and displayed on a pre-formatted page ready to accept the data.  

While the benefit of being able to display data from your AMS (or other third-party systems) on your website is great, this method is the more manual and rudimentary (and many times less expensive) way of achieving this. The drawbacks, of course, are that the data is not real-time and any changes to your committees or board members’ information (keeping with this example) would not be reflected on the web page until the next new upload process took place.