First sign in behavior
I'm self hosting Twenty on a Coolify's instance.
The soft works nicely BUT I'm experiencing issues with system emails (I've made another post about it).
As I can't send email invitation to the workspace, I'ce tried the journey of a team member willing to join the workspace.
I've disabled signup, so only email addresses registered can signin, that's a good start.
But if a member, who signing in for the first time, goes to the instance URL "crm.<domain.tld>" WITHOUT using the invitation link, the instance detects it as a new connexion and offers to create a new workspace...
I know this would be avoided if the system emails worked, but the behavior would still be there if member's does not use the invitation link.
I have multiple question then π :
- Is it expected behavior?
- Can we list all the workspaces created on an instance as a super admin or something?
- Can we link multiple workspaces together?
- Can we disable the workspace creation?
Thanks a lot for your time.
Love your job on Twenty β€οΈ
14 Replies
Hey @Neruu2, if you cannot send email on your instance, you can use the invitationLink (which is basically what we send in the invitation email)
For that go to settings > Members and copy the invitation link. You then can send it to your members
Thanks for the answer.
Yes, that's what I'm using at the moment to onboard members and it works. But as I've said, this does not block the behavior that, if users arrive, on their first connexion, on the instance url WITHOUT the invitationLink, the instance will detects them as first connexion and make them create their own workspace.
This can be confusing, especially regarding the fact that it seems we can't have an overview of the workspace created?
ok, are you sure your environment variable
IS_SIGN_UP_DISABLED is set to true?Certain of it.
This only happens for users that I want to invite (so their email addresses are registered as members).
If addresses are not registered, I get the correct message "signu is disabled"
Mmmh, ok, there might be an issue somewhere then
@AMoreaux what do you think?
To add more context:
I add a member (with its email address).
If that member tries to connect to the instance WITHOUT the invitationLink (no token then), first connexion will trigger the workspace creation.
If the email address is not registered (in the members) and the user tries to connect with it, correct "sign up is disabled" message appears.
yes i got it
It looks related to a recent feature of invitation email
Clearly not at all blocking for me, the invitationLink work around is more than enough for my case, but I supposed this was not expected behavior.
Yes thank you for reporting it
Trying to reproduce.
- set
IS_SIGN_UP_DISABLED=true
- connect to [email protected]
- creating an invitation to [email protected]
- logout
- create a new account with [email protected]
- receiving the proper error signup is disabled
Also tried with a gmail address and a google connection, same proper error signup is disabled
What did I missed?OK I just retried on my instance and got same result as you...
Maybe some delay in the app behavior (as I changed the value of
IS_SIGN_UP_DISABLED between version)
Anyway, sorry should have retested ityou need to restart the server for the env var updates to be taken into account
no problem
yep that I did (coolify warns you when your config is different than the currently running container).
Thanks a lot for your help β€οΈ
My pleasure!
@AMoreaux no issue in the end
I like this kind of bug fix π