Purpose: This article will walk you through best practices when using SAML 2.0 authentication to access the Orion API. Simple Use Case: An existing user within a customer’s Advisor portal,…
Continue Reading
Purpose: This article will walk you through best practices when using basic authentication to access the Orion API. This method is used for simple changes made by an API user or…
Purpose: This document covers the process to make an OAuth connection to the Orion API for an Orion user. To log in to the API as a partner API user,…
Purpose: Orion supports several methods for authenticating to the Orion Connect platform or the Orion API including basic, SAML 2.0, and OAuth. In each case an Orion ID and Secret…
https://oas.force.com/BrinkerSupport/s/article/Orion-Mapping-to-Orion-Planning The below mapping information provides the data sync from Orion Connect to Orion Planning. When reviewing these fields, always reference this table to ensure you are looking in the…
Orion Connect The core Orion Connect data model was designed around the original purposes of the Orion platform for portfolio management and performance reporting. This data model still provides the…
For Orion’s core applications, each individual person, connection, or integrations should have its own individual user tied to that entity. User management allows for custom and specific access to collections…
Purpose: This article will outline how to create new portfolios within the Orion system. Households are one part of a Portfolio, the other two records being a Registration and an…
Purpose: This article will outline how to create a new Representative entity within the Orion system. In Orion Connect the Representatives are the registered advisor that has a book of…
There is a very powerful but often confusing feature in the reporting system called Unmanaged. This feature is often thought of as a way to mark an asset, product, or…