Organisation name & logo
Approved tenant or reseller workspaces can use their own display name, logo, favicon and related brand assets.
Multi-tenant & reseller readiness
Your brand on the front. Controlled platform architecture underneath.
AI Tech solutions are being structured so approved organisations and resellers can present selected services under their own identity without weakening tenant isolation, role controls, onboarding rules or operational security.
Branding scope
What can be adapted for an organisation or reseller.
Branding is treated as a presentation layer. It should not alter the platform’s tenant boundaries, permissions, messaging controls or operational activation rules.
Brand colours
Primary, secondary and supporting colours can be configured within accessibility and usability limits.
Client-facing contacts
Support phone, email, address and selected help links can be presented using the tenant or reseller’s public identity.
Portal presentation
Authenticated workspaces can present tenant-specific branding while preserving the same controlled account lifecycle and security model.
Branding is not permission.
A custom logo, domain or theme never grants additional messaging access. Operational privileges remain controlled by the account’s organisation, role, lifecycle and operational status.
Domain architecture
Separate marketing, operations and future client domains.
Domain separation helps keep public information, authenticated operations and future white-label experiences easier to manage.
aitech.co.keAI Tech public marketing, company information, service pages, trust content and enquiries.Public website
messaging.aitech.co.keAI Tech Messaging signup, onboarding, client login and operational workspace.Operational portal
api.aitech.co.keReserved architecture for controlled application/API access as the platform expands.API layer
developers.aitech.co.keReserved architecture for future developer documentation and integration guidance.Developer layer
{client-domain}Future white-label domains can map an approved tenant or reseller identity to the correct workspace after DNS, TLS and tenant-domain verification.Custom-domain readiness
Tenant & role model
Brand separation follows organisational separation.
White-label architecture is most useful when branding, users, permissions and data all resolve to the correct organisation.
PlatformAI Tech Master Administration
Controls platform-level configuration, organisation provisioning, operational safeguards and approved reseller/customer relationships.
ResellerReseller Administration
Where enabled, manages its own branded client environment within permissions granted by AI Tech.
OrganisationOrganisation Administration
Manages the organisation’s staff users, approved Sender IDs, campaigns and operational settings within its tenant boundary.
StaffSupervisor / Staff / Accounts
Receives only the access required for assigned duties, with actions attributable to the individual user.
Security boundary
White-label presentation must never expose provider infrastructure or secrets.
Branding affects the interface. Sensitive provider operations remain server-side and outside the client-facing presentation layer.
Tenant isolationUsers and records must resolve to the correct organisation before tenant data is shown or changed.
Role enforcementBranding does not bypass platform, reseller, organisation or staff permissions.
Server-side credentialsProvider API credentials, passwords and encryption material remain outside public pages and client-facing configuration.
Provider abstractionClient-facing workflows use AI Tech platform terminology instead of exposing upstream provider infrastructure.
Operational activationBranded accounts remain locked until verified provider, credential, sync and Sender ID prerequisites are satisfied.
AuditabilityImportant onboarding and operational actions remain attributable even when a tenant uses its own branding.
Implementation model
A controlled path from AI Tech branding to a client-branded experience.
Custom branding and domains should be introduced only after the organisation exists, its role model is clear and the destination domain has been verified.
- 1
Organisation / reseller setup
Create or verify the tenant organisation and confirm whether it operates as a customer or approved reseller.
- 2
Brand configuration
Confirm organisation display name, logos, colours, public support contacts and whether “Powered by AI Tech” should remain visible.
- 3
Domain verification
Validate ownership/control of the requested domain and complete DNS/TLS setup before directing users to it.
- 4
Tenant routing
Map the verified hostname to the correct tenant without using the hostname alone as an authorisation decision.
- 5
QA before launch
Test branding, login, tenant isolation, role permissions, links, mobile behaviour and operational restrictions before public use.
Readiness status
Architecture-ready does not mean every custom domain is already active.
AI Tech can prepare tenant branding and custom-domain implementations progressively. Each production domain still requires its own configuration, verification and launch QA.
Brand configuration matrix
Brand settings should be explicit, validated and reversible.
The tenant UX should resolve identity from a controlled configuration record rather than hard-coded organisation names, colours or contact details.
IdentityOrganisation display name, portal display name, logo, white logo and faviconFallback: AI Tech default
ThemePrimary, secondary and accent coloursFallback: accessible AI Tech theme
SupportPhone, email and locationFallback: AI Tech support
AttributionOptional “Powered by AI Tech” presentation according to agreementDoes not change platform ownership or permissions
DomainVerified hostname mapped to the intended tenantFallback: AI Tech portal domain
Interactive demonstration
Preview a tenant-branded workspace without changing a live account.
Try organisation names, colours and support contacts in the browser-only branding preview.