• What providers does Flowcode Offer?

    • We offer Azure, Okta, and Google as an SSO identity provider

  • I have another provider, can I use them?

    • Have your IT team reach out to us if you wish to use another provider.

  • Can I immediately turn SSO on?

    • The process is quick, but both you and your CSM do have a few things to set up to make it happen. Please give a 7 day leeway prior to SSO launch.

  • Can any member of an organization sign on with SSO?

    • No, members have to be listed by the company. That is the beauty of SSO, it lets you determine who gets access and who does not get access to Flowcode vs. manually removing people from orgs. Any employee could attempt to signup with their email, but if it is an email domain we have listed as an SSO client they will be blocked from signing up with their work account and told to contact an admin from their team.

  • So if I am on the list for SSO how do I log in?

    • You just log in exactly how you normally would. Visit flowcode.com/signin. When you enter your email the password piece to logging in will disappear and you will be prompted to click SSO. This will work whether or not you have logged in before.

  • If I make a code on the homepage generator and then try to create an account and I am in an SSO company what happens?

    • You will lose the code you created, but you will be able to log in to your new account

  • Are admins and members treated differently for this?

    • Nope. If you are invited as an admin you will be an admin when you first sign in via SSO. If you were invited as a member, it will be the same.

  • What happens if I leave the company of an SSO-enabled org?

    • Your IT department will remove you from the Identity Provider (Azure/Okta) so you lose access to all of your applications, Flowcode included. But while you won’t be able to access you account, we still recommend the Org Admin manually remove you from the org so all your assets get transferred back to the admin.

Did this answer your question?