What a custom domain means
A custom domain lets your clients open your portal from a branded address instead of only using a KorpKit default link. This makes the portal feel more professional and more connected to your business.
For example, a business may want clients to visit a subdomain like portal.yourbusiness.com. The exact domain or subdomain depends on what the tenant owns and configures.
Custom domain access is package-based. Free tenants can use the default KorpKit portal link. Paid tenants can unlock stronger white-label domain setup depending on the package.
Before you start
Make sure you own the domain. You must be able to edit DNS records for that domain in the place where the domain DNS is managed, such as Cloudflare, your domain registrar, or your hosting DNS panel.
Decide whether you want to connect the root domain or a subdomain. A subdomain is usually safer for a portal because it keeps your main marketing website separate from the client portal.
Do not delete existing DNS records unless you understand what they do. Removing the wrong record can break your website, email, or other services.
Step 1: Open domain settings in kkx0101
Log in to the KorpKit tenant control panel and open the custom domain or configuration area. This is done from kkx0101 because domain setup belongs to the tenant account, not the client portal itself.
Enter the domain or subdomain you want to connect. The system should show the DNS records required for verification and routing.
Copy the records exactly. DNS is sensitive. A missing dot, wrong name, wrong value, or wrong record type can stop verification.
Step 2: Add DNS records
Open your DNS provider and add the record shown by KorpKit. The record may be a CNAME, TXT, or another required record depending on the setup flow.
The name/host field and value/target field must match what KorpKit shows. Some DNS providers automatically add the domain name at the end, so read the provider interface carefully.
If you use Cloudflare, also pay attention to proxy settings if the KorpKit instructions mention them. Some verification flows require DNS-only behavior until verification is complete.
Step 3: Wait for DNS propagation
DNS changes are not always instant. Sometimes they work in a few minutes. Sometimes they take longer depending on the provider, cache, and previous DNS settings.
If verification fails immediately, do not panic. Recheck the record values first, then wait and try again.
Avoid adding many duplicate records while waiting. Duplicate or conflicting records can make troubleshooting harder.
Step 4: Verify the domain
Return to kkx0101 and run the domain verification action. The system checks whether the DNS records can be seen publicly and whether they match what KorpKit requires.
If verification passes, KorpKit can connect the domain to the tenant portal. If verification fails, compare the DNS record type, name, and value again.
Verification exists to prove that you control the domain and that the domain is safe to connect to the tenant portal.
Step 5: SSL and final testing
After the domain is connected, SSL may need time to issue. SSL is what makes the address open with https instead of showing browser security warnings.
Open the domain in a private browser window and test the portal. Check that it loads the correct tenant, shows the correct branding, and does not redirect to the wrong business.
Also test login, client signup if enabled, file upload, invoice link, and email notification links after connecting a domain.
Common domain problems
The most common problem is using the wrong DNS record name. Another common problem is adding the right value under the wrong record type.
A third common problem is connecting the wrong domain level. For example, adding a record for yourbusiness.com when the portal is supposed to use portal.yourbusiness.com.
If email stops working after DNS edits, check whether you changed mail records by mistake. Portal domain records and email records should be handled carefully.
Simple summary
Choose the domain or subdomain, enter it in kkx0101, copy the DNS records, add them at your DNS provider, wait for DNS, verify inside KorpKit, then test the portal.
Do not guess DNS values. Use exactly what the system gives you.
Once complete, clients can use your branded portal address to access the KorpKit-powered client portal.
