The client portal is where your onboarding entities verify their identity, sign agreements, and complete their KYC forms. Your deployment has one at https://yourcompany.getdal.sa/portal by default. This guide covers serving the portal from a domain you own, and building portal links that pre-select an entity’s identity verification method.

​
How Entities Reach the Portal

An entity signs in with the email address on its record and a one-time code sent to that address. There is no password and no per-entity link to generate — opening the portal URL in a browser is enough to start the journey. When email invitations are enabled on the KYC flow, DAL emails the entity a link. That email always points at the default portal URL. If you want entities to land on your own domain, or on a pre-selected verification method, send them the link yourself.

​
Serving the Portal From Your Own Domain

The portal can be served from a subdomain you own, so entities stay on your brand for the whole of onboarding. The portal, its content, and its data are unchanged — only the address differs.

​
1. Choose a Subdomain

We suggest portal.yourcompany.com (or .sa) for consistency, but any subdomain works. It does not need to contain your company name; we map the domain to your account explicitly when we register it. Use a subdomain rather than your main domain (yourcompany.com), which usually cannot hold the CNAME record required in step 3.

​
2. Ask DAL to Register It

Email support@getdal.sa with the subdomain. We register the domain against your company and allow it as an API origin, then reply with the CNAME target to point at.
Registration and DNS are separate steps and both are required. Until we register the domain, requests from it are rejected as an unrecognized origin even if DNS already resolves.

​
3. Add the CNAME Record

At your DNS provider, add a CNAME record from your chosen subdomain to the target we returned in step 2. Once it propagates and the certificate is issued, the portal is live on your domain.
Point the CNAME directly at the target we give you.

​
The Entry URL Changes Shape

On your own domain the portal is served at the root. There is no /portal path segment. https://portal.yourcompany.com/portal is not a valid portal URL. The default domain keeps working after your own domain goes live — both serve the same portal against the same account.

​
Pre-selecting the Identity Verification Method

When identity verification is enabled on an entity’s KYC flow, the entity is first asked whether it is a KSA resident or an international client. The answer decides which verification path it takes: You usually know which applies already, because you created the entity. Add the idv_method query parameter to the portal link and the entity is not asked: it sees the chosen method as a confirmed step and continues straight into it. The parameter goes on the portal entry URL, which differs by domain:
  • Default: https://yourcompany.getdal.sa/portal?idv_method=international
  • Your own domain: https://portal.yourcompany.com/?idv_method=international
On your own domain the portal is at the root, so https://portal.yourcompany.com/portal?idv_method=international will not work. Build the link against /.