This message was deleted.

Hey @nice-planet-7734 this looks like a bug on our end, we’ll work on a fix today and let you know when it has been completed.

The samples in the API doco are sufficient for now. I'll let you know if I need more

I'm sure I follow what you mean @nice-planet-7734 . Do you mean Google SSO or something else?

Yes Google SSO

You can login with Google on the login page. If you’ve used email you can still login via Google and it will link the account you already have.

Sorry not an expert on this matter. We want to manage our users in our google suite instead of creating the users directly in Secoda

For Secoda you can think of the Google SSO as a way for Secoda to know which users are part of your Google suite. For example: • Say there’s Employee A who is part of your Google Suite • When they log in with Google SSO Secoda is linking to that user’s details • When Employee A is removed from your Google Suite they will no longer be able to log into Secoda. In order for that user to work properly in Secoda, we make a copy of their details in our database along with supplemental properties that our app requires. That’s why when you remove them from the Google Suite you can still see them in Secoda, but are not able to log in. Hopefully that provides some clarity.

That's good info. The part which I'm missing is can we add the users in our Google Suite and it automatically create a user in Secoda? Or do we always need to send an invitation from Secoda?

It depends, if you want them to be a certain role you’ll need to invite them. Otherwise, if they use Google SSO to login and their email domain matches with yours then they can automatically join the workspace as a viewer. From a security perspective we require emails to be verified so someone can’t just put in <name>@courseloop.com and join your organization, they actually have to be part of your Google Suite. The only thing you need to do is add your domain to Settings > Workspace > Allowed Domains and add courseloop.com