Sageflo Radiate - Partner Docs

[asmithsageflo]

Pull Request/Issue Resolution

Description of Change:

Added new partner doc for Sageflo

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that you haven't removed any images (replacing an image with an updated one of the same name is fine), as this breaks the French site
• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @timothy-kim and @KellieHawks as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @timothy-kim or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@josh-mccrowell-braze	Monolith Deployments Quality Infrastructure Platform Infrastructure Datalake SDKs
@KellieHawks	Currents Internal Tools Product Partnerships SMS Customer Lifecycle, Identity and Permissions
@bre-fitzgerald	Reporting Intelligence User Targeting IAM Channels FIX
@lydia-xie	Ingestion Core Objects Core Messaging Messaging and Automation Email (Composition and Infrastructure)

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Aaron Smith.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[vercel]

Someone is attempting to deploy a commit to the Braze Team on Vercel.

A member of the Team first needs to authorize it.

[KellieHawks]

@asmithsageflo Closing this PR as your documentation has been addressed in a separate PR (#4837) as we ran into some Github permissioning issues during the review phase. Feel free to follow up with any questions!

-The Braze Documentation Team