This topic was automatically generated from Slack. You can find the original thread here.
We just upgraded to the Business tier, and we were hoping to start using SAML SSO, rather than Google OAuth.
But the SAML configs seem too limited. 
Here’s what we see:
But normally, we would expect multiple fields, like this:
And we would also need this information from Pipedream in order to setup the SAML application on our side:
Usually, both the ACS URL & Entity ID are the same (as in the case of https://dbc-12345678-abcd.cloud.databricks.com/saml/consume above)
The main goal for this would be to enable the org to manage application access on the SAML side, rather than in the application itself.
Right now, I could give access to Pipedream to anyone in our org.
yeah good call, I can improve our docs on this. Now that you’re on the Business plan, do you want us to set up a private Slack Connect channel so we can discuss details specific to your workspace?
I think we’re fine with using the community slack, so up to you!
I guess there’d be a bit more continuity in a Slack Connect channel.
it’s a little easier for our Support team since we prioritize all Slack connect channels. I love all the questions you’re asking in public though
Ok, sounds good!
on this question, we looked into it and the SAML metadata URL should actually provide all of that: SAML metadata - Wikipedia
do you see an option to copy a SAML metadata URL?
the ACS URL I’m looking into
We’ve never used a SAML metadata URL before, so I’ll have to look into that! 
Regarding the SSO documentation, I did find the doc for Okta & Google OAuth, but not SAML.
Can you use these values:
• ACS URL: https://api.pipedream.com/auth/saml/consume
• Entity ID: https://pipedream.com/@ (the URL-safe org name you’d see in e.g. your workflow URLs)
I’ll improve all these docs, lmk if that works though
then once you create a Pipedream SAML app on your end, I think you should see the metadata URL somewhere