You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created the first user alexandre so it's the one being admin.
I wanted to create a user but #137 prevents it.
So I used the registration form on another browser to create another user test.
But the new user test is not a normal user attached to the same enterprise as alexandre, instead it created a new separated tenant where test is the administrator, like if it was for another company.
So I have alexandre administrator of tenant 1
And test administrator of tenant 2
I guess this is the expected behavior since it's an app meant for freelancer first, but during registration there may should be an option to join a tenant / company / enterprise that already exist with a code or a pending validation or something?
However those tenant are not really separated, because when you check Public for a project it will be really public and accessible to all users from all tenants and not only the users from your tenant. Which make me think that the multi-tenant thing is maybe not expected and it then means that every users that self-register is admin.
The text was updated successfully, but these errors were encountered:
I created the first user
alexandre
so it's the one being admin.I wanted to create a user but #137 prevents it.
So I used the registration form on another browser to create another user
test
.But the new user
test
is not a normal user attached to the same enterprise asalexandre
, instead it created a new separated tenant wheretest
is the administrator, like if it was for another company.So I have
alexandre
administrator of tenant 1And
test
administrator of tenant 2I guess this is the expected behavior since it's an app meant for freelancer first, but during registration there may should be an option to join a tenant / company / enterprise that already exist with a code or a pending validation or something?
Also this behavior may be documented on the wiki, it's not mentioned on this page https://wiki.titra.io/books/administration/page/user-administration.
However those tenant are not really separated, because when you check
Public
for a project it will be really public and accessible to all users from all tenants and not only the users from your tenant. Which make me think that the multi-tenant thing is maybe not expected and it then means that every users that self-register is admin.The text was updated successfully, but these errors were encountered: