Creating a Tenant (backend)
Creating a tenant in your Concord CRM SaaS setup is a streamlined process that allows you to provision new CRM instances with control over modules, database schemes, and package assignment.
Last updated
Creating a tenant in your Concord CRM SaaS setup is a streamlined process that allows you to provision new CRM instances with control over modules, database schemes, and package assignment.
Last updated
From the SaaS dashboard, go to the Tenants section in the sidebar or top menu. Click the “Create Tenant” button to open the creation form.
Name
Enter a unique name for the tenant. This name is used internally to identify the tenant instance.
Customer
Use the auto-complete search to find and select an existing contact that will be associated with this tenant. This customer will receive notifications and serve as the primary contact.
Subdomain
Provide the subdomain where the tenant’s CRM will be accessible (e.g., acme.yourcrm.com). This is required if subdomain registration is enabled.
Domain
(Optional) Set a custom domain for the tenant (e.g., crm.acme.com). Ensure proper DNS and cPanel configurations if using a custom domain.
Activate Modules
Select the non-core modules that should be activated for this tenant. Only modules with extended licensing will be auto-activated.
Disable Modules
Select the non-core modules that should be disabled for this specific tenant, even if globally available.
Disable Core Modules
Select any core modules (e.g., Deals, Contacts) that should be disabled for this tenant. Disabling core modules can significantly affect the CRM’s functionality.
ℹ️ Use this with caution and only when certain core functionalities are not required by the tenant.
Choose the preferred database scheme for the tenant's data storage from the following options:
Use the current active database: All tenants share one database; tables are separated by unique prefixes.
Auto-detect from client subscribed package: Uses the DB strategy defined in the assigned package.
Create a new database: A dedicated, isolated database is created automatically for the tenant.
I will provide my own credentials: Manually provide database connection credentials (fields will appear).
Use tenant ID as table prefix: Stores tenant data in the shared database with a prefix based on tenant ID.
➤ Additional Fields (when "I will provide my own credentials" is selected)
permissionDB Host: Hostname or IP of the target database server.
DB Port: Port used for database connection (usually 3306 for MySQL).
DB User: Username with permission to access the database.
DB Password: Password for the DB user.
Database: Name of the specific database that will store the tenant’s data.
Select the package to assign to this tenant. The selected package will determine:
Module and quota limits
Pricing and billing cycle
Trial and expiry settings
Review all the entered details:
Ensure the correct customer is selected
Check that the subdomain/domain is properly configured
Confirm module activations and restrictions
Verify the database scheme and credentials
Click “Save” to finalize tenant creation. The system will now:
Provision the database as per the selected scheme
Activate/deactivate relevant modules
Link the tenant to the selected package
Generate login access on the specified subdomain or domain
💡 Note for Unmanaged Server Users: If you're deployed on an unmanaged VPS or dedicated server, we provide step-by-step instructions customized for the tenant along with ready-to-use automated provisioning scripts that can handle subdomain creation for your tenants. This includes instructions to add DNS record and on how to use download and use the automated script. This will be helpful, if you do not want to setup wildcard subdomain. You can download these resources by clicking “Download Instructions” on the tenants list page.
⚠️ Warning for Plesk Users:
Plesk Integration Is Manually Supported If you're using a server with Plesk, note that automatic domain creation, subdomain provisioning, and MySQL database/user creation will not work out of the box. You must manually:
Create the domain or subdomain.
Point DNS entries correctly.
Create the database and assign the user manually.
Ensure database credentials match what is entered during tenant creation (if using "I will provide my own credentials").