[ **Multi-Workspaces and single subdomain** ] - is possible? (no subdomain)
Hello, everyone!
I’d like to know if it’s possible to disable the subdomain option when Multi-Workspaces is set to TRUE.
I currently use several subdomains on my hosting, but I’d like to point twenty to a
single subdomain while keeping the Multi-Workspaces option enabled.
Is this possible? If so, how can I do it?
I saw on GitHub that an update is in progress, which will allow managing user rules. With this feature, will it also be possible to define which workspaces a specific user can manage and view?
Many thanks!
12 Replies
I’d like to know if it’s possible to disable the subdomain option when Multi-Workspaces is set to TRUE.I believe it's impossible as now each workspace has to have it's own subdomain due to implementation of this feature @AMoreaux could you confirm this? ^
I saw on GitHub that an update is in progress, which will allow managing user rules. With this feature, will it also be possible to define which workspaces a specific user can manage and view?It's already possible as each user (except for the first user creating new workspace, so-called "admin") has to be invited in order to have an access to specific workspace, so if someone wants to have an access to 2 workspaces, user must be invited to both of them by someone with access
Yes, the implementation of multi workspace is only with subdomains. What’s your use case that implies to use multi workspaces without subdomain?
I just read the full message where you answer to my question: You could use another subdomain like crm.your-domain.com so subdomains will be prepend on it.
Is it acceptable?
Guys, many thx!
I kept Multi-Workspaces enabled (TRUE), but I already use other subdomains within my main domain.
Example:
app.mydomain.com
mail.mydomain.com
pay.mydomain.com
When this option is set to TRUE, it rewrites the main subdomain "app.mydomain.com" to "crm.app.mydomain.com" and not created this "crm.mydomain.com"
I can't set a URL on my root domain because it would overwrite my main website: mydomain.com.
I tried to fix this by pointing the main URL to app.mydomain.com, but I'm not sure if this is the correct approach.
Please, could you help me with this?
I use my installation via Docker Portainer, but I'm completely new to this, and I'm a bit lost when it comes to configuration.
version: "3.7"
services:
twentycrm_server:
image: twentycrm/twenty:latest
volumes:
- twentycrm_data:/app/packages/twenty-server/.local-storage
- twentycrm_docker:/app/docker-data
networks:
- my_network_app
environment:
- PORT=3000
- SERVER_URL=https://app.mydomain.com
- FRONTEND_URL=https://app.mydomain.com
- DEFAULT_SUBDOMAIN=crm
- IS_MULTIWORKSPACE_ENABLED=trueWhy do you think about a config like that:
So the home page will be https://default.crm.mydomain.com
And workspaces pages will be https://workspaceSubdomain.crm.mydomain.com
PS: As you said you can't use multi workspace without subdomains by workspaces
Hi, can someone explain how multi-workspaces work? I am trying to run it with docker compose and Twenty CRM keeps creating random domain names. I would like to have specific domains and workspaces and create workspaces myself, not created workspaces for every first user....
Is this already working?
Hi
When a user signup, he can be on an workspace or on home.
If he is on the default subdomain, it mean he is on home page, so the signup will create a new workspace
If he is on a workspace subdomain, he will signin or signup in this workspace.
You can change the subdomain of each workspaces in workspace settings.
You can invite people in settings too.
Yes it works and it's use on twenty.com
How to make domain names manually configured, predictable?
By domain you mean workspace subdomain ?
yes. I configured manually domains like microsoft.crm.example.com, apple.crm.example.com in NGINX with default default.crm.example.com and SERVER_URL=crm.example.com etc
but when I go and create a user it redirects to something random like snow-flake.crm.example.com
Ok so keep SERVER_URL like that
And use a wildcard for *.crm.example.com in nginx
I don't have a wildcard HTTPS yet, so can only set specific hostnames
So you will need to update the workspace subdomain without https.
In setting using http or directly in database
Today you can't define the workspace subdomain during the creation