Organisation constituents

Hi there, I'm Bob, one of the co-founders of Bridgit. In this short video I'll share how Bridgit handles organisation constituent records when integrating data between Raisely and Raiser's Edge NXT.

To begin, I'm going to navigate to our test Raisely campaign and sign up as an organisation. By default, Raisely expects a user to be associated with an organisation. I need to give the organisation profile a name, and I'm going to skip the optional fields.

With that complete, I'm going to navigate to our Bridgit portal, select the bridge for our general appeal in Raisely to the NXT sandbox, and click Run Bridge. With that triggered I'll pause the video and return in about a minute once it's completed.

So I'm back. Our bridge run has completed, and if I navigate to our NXT sandbox I can see one of the two constituent records that have been created. This is the organisation record, and it reflects the basic information provided through Raisely.

We also have the Raisely profile ID here, stored as an alias, which allows us to strongly link this record in NXT to any future activity on the Raisely platform.

Scrolling down, we can see the relationship that has been created between the organisation constituent and the individual constituent, including a type and a description that are both configurable.

That is how organisation constituents are managed when integrating data between Raisely and Raiser's Edge NXT via Bridgit. Thanks for watching.