Enhancing Consistent SSO Integration Across Multiple Redtail Databases

Background:

CPS Investment Advisors services external Co-advisor firms, culminating in our establishment of a primary home Redtail database along with 24 supplementary Redtail databases. While with Orion we have a single unified database, Redtail specifically suggested the deployment of distinct databases as the only way to partition clients. This ensures each outside co-advisor firm we service only sees their own designated clients. This proposal was grounded in the commitment that navigating between these databases would be fluid by “Switching” into our other Redtail databases in managing all clients that we service across all databases. Please reference Case # 05770177 where support concludes that “The integration is designed to work when connected to one database and is not intended for use when switching between other databases.”

Problem Statement:

When we integrate the SSO of our primary (home) Redtail database with the Orion platform, or any other platform, the integration remains intact and functions normally. However, challenges arise when these users switch to another Redtail database. In these instances, the system prompts users to re-integrate SSO, which initially appears to function. Yet, by the following day, not only is the new integration within the "switch" database disrupted, but the SSO integration in the primary home database is destroyed, effectively resetting the integration process for all databases.

Proposed Solution:

1. Persistent SSO across databases: The platform should enable a user’s home database SSO configuration to be consistently and reliably applied when switching into any co-advisor database.

2. Flexible SSO Configuration: Possibly introduce an option allowing external users of a database to either utilize their home database SSO credentials or establish unique SSO integration credentials for that specific database. This would help cater to varying integration preferences and requirements across databases.

3. Protect Home Database Integrity: Any integration activity in a database for which the user is an External User should not compromise or interfere with the SSO settings of a user’s home database.

Expected Benefits:

1. Operational Efficiency: Facilitating a consistent SSO experience would circumvent unexpected disruptions, paving the way for efficient daily workflows.

2. Enhanced Client Servicing: A robust integration means we can service clients across all databases, void of any obstacles.

3. Enhancement Of All SSO Integrations: We experience the same SSO failures with trying to integrate Redtail to Wealthscape, completely disabling the “Set Up New Account” SSO workflow to Fidelity. This is an integration we were very much hoping to use. We are now planning to use the Orion to Fidelity new account workflow once it is fixed.

Impact Analysis:

The inconsistencies in the SSO integration can necessitate manual re-entry of information across platforms. This manual duplication process inherently increases the risk of human errors, leading to potential discrepancies and inefficiencies. Moreover, our inability to interact with our co-advisor databases in the same intuitive manner as home users significantly hinders our capacity to showcase the benefits and functionalities of SSO integrations to them. This situation not only strains our internal processes but also places us at a distinct disadvantage during collaborative efforts and demonstrations. It would also be unreasonable to suggest that we set up all our employees that need “switch” access to another database we own, as home users of each database, and instead of switching, they log out of their home database and log in as a home user of each of our 25 databases in order to service all the portfolios we maintain.

Future Implications and Dependencies:
As our firm grows adding more outside co-advisor groups, and technology advances, seamless integration between platforms becomes more than just a convenience; it's an operational necessity. With specific reference to Redtail and Orion:

1. Redtail CRM & Redtail Imaging: How will external users of a Redtail CRM database access the corresponding Redtail Imaging database? Has this been considered?

2. Orion Document Vault & Redtail Imaging: As Orion moves to utilize Redtail Imaging for its Document Vault, any disruptions or inconsistencies in SSO integration could prevent our team from accessing vital client documents stored in the vault. This not only hinders our internal operations but can also jeopardize timely client servicing, which relies on access to these crucial documents.

3. Orion Client Portal Implications: The limitations in SSO integration could have future repercussions in Orion’s client portal access should an integration be forthcoming there.

4. Other Platform Integrations: Beyond just Redtail and Orion, the SSO integration issue could potentially hinder our integration with other platforms, such as LaserApp, PreciseFP, PDF.co or ShareFile. Such disruptions can lead to inefficiencies and, in worse scenarios, data inconsistencies or losses.

5. Anticipated Growth and Scalability: As we foresee more co-advisor collaborations and potentially new platforms being added to our ecosystem, the current SSO limitations can become a more significant bottleneck. Addressing it now will pave the way for smoother expansions in the future.

Conclusion:

In an age of digital integration, the harmonious interplay between platforms is pivotal for operational efficiency, client servicing, and future scalability. While the alliance between Redtail and Orion is undoubtedly paramount, our concerns transcend this singular partnership. It is imperative to recognize that the challenges faced in SSO integration have ripple effects across our entire tech stack, affecting integrations with platforms like LaserApp, PreciseFP, PDF.co, ShareFile, and more. Addressing these concerns ensures not only an enhanced user experience within Redtail and Orion but also secures the integrity and fluidity of our operations across the board. We advocate for a solution that not only leverages the combined strengths of individual platforms but also fortifies the interconnected web of systems that our operations rely on.