This message was deleted.
# secoda-supportw
wooden-spring-14915
10/27/2023, 4:43 PMThis message was deleted.
✅ 1
m
mammoth-lamp-67488
10/27/2023, 4:44 PMHi Kevin, let me take a look!
mammoth-lamp-67488
10/27/2023, 4:49 PMI believe the limitation here is that our system looks at the domain of the email first, and if there are no Allowed Domains set up in your workspace, and the user hasn't been explicitly added by their email, it will redirect them to a new workspace.
This logics ensures that not just anyone with a link can join the workspace, but let me see what we can do to toggle the logic on and off!
mammoth-lamp-67488
10/27/2023, 4:50 PMFor additional context, here is where you can find Allowed Domains for your workspace.
a
abundant-crowd-2724
10/27/2023, 4:50 PMOk, that makes sense. Perhaps in place of that an email could be issued to admins when a new user join with the link. If that logic is toggled off.
m
mammoth-lamp-67488
10/27/2023, 4:51 PMI'll share that feedback with the team!
a
abundant-crowd-2724
10/27/2023, 4:54 PMSpeaking of creating users... can you confirm its still not possible to create users via the API with a group? Docs show only Teams.
m
mammoth-lamp-67488
10/27/2023, 4:59 PMWe just updated our docs for User Groups. It would be two API calls - one to create the user, and another to add them to an existing user group.
mammoth-lamp-67488
10/27/2023, 5:00 PMPS the ticket for tracking improvements to the email domain logic can be found here. I'd recommend upvoting it to stay up to date!