Rewrite Okta SAML docs for application owners

[alexisintech]

🔎 Previews:

• https://clerk.com/docs/pr/2155/authentication/enterprise-connections/saml/okta

Followup from #2112

What problem does this solve?

Here's how configuring SAML usually works:

1. An App Owner begins to onboard a new enterprise, and is put in touch with the enterprise's IT Admin
2. The App Owner creates the saml connection, and shares the Single sign-on URL and Audience URI (SP Entity ID) with the IT Admin via an email, along with more instructions
3. The IT admin follows those instructions, and responds via email with a metadata url
4. The App owner adds the metadata URL, and then coordinates on a time with the IT admin to enable and test the connection

Our docs today don't reflect that reality. They presume the the reader has simultaneous access to Clerk and the Okta IDP. As such, an application owner reading our docs needs to understand them deeply enough to re-write them into an email suitable for the IT-admin's consumption. This is time consuming and painful, because the App owner wants to avoid needing to internalize the nitty-gritty details of SAML - that's why they have Clerk!

What changed?

This rewrites the docs with the two above personas in mind.

The Application Owner is the primary reader, with access to Clerk. The instructions for the IT Admin (with access to Okta) are encapsulated in an email template.

Checklist

• I have clicked on "Files changed" and performed a thorough self-review
• All existing checks pass

[github-actions]

Hey, here’s your docs preview: https://clerk.com/docs/pr/2155

[SarahSoutoul]

Looking goood! Left a few suggestions 🚀

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
clerk-docs	Ready	Preview	Aug 25, 2025 7:24pm

[LauraBeatris]

Looking good! I've reviewed the steps from the Okta side as well and it's correct.