Subdomain Configuration
Configure your organization’s subdomain and optional custom domain.
Overview
Every ProBeya organization operates on its own subdomain: your-org.probeya.com. This provides complete isolation between tenants and a branded URL for your team.
Default Subdomain
Your subdomain is set during organization creation. It must:
- Be between 3 and 63 characters
- Contain only lowercase letters, numbers, and hyphens
- Start with a letter
- Not end with a hyphen
- Be unique across all ProBeya organizations
Changing Your Subdomain
Changing your subdomain will break existing bookmarks, shared links, and API integrations. Proceed with caution.
To request a subdomain change:
- Go to Settings > Organization > Subdomain
- Enter the new subdomain
- Confirm availability
- Submit the change request
The old subdomain will redirect to the new one for 30 days. After that, the old subdomain is released.
Custom Domain
Business and Enterprise plans can configure a custom domain (e.g., pm.yourcompany.com) to replace the default your-org.probeya.com.
Add Your Domain
Go to Settings > Organization > Custom Domain and enter your desired domain (e.g., pm.yourcompany.com).
Configure DNS
Add a CNAME record pointing your domain to custom.probeya.com at your DNS provider.
Type: CNAME
Name: pm
Value: custom.probeya.com
TTL: 3600
Verify Domain
Click Verify in the ProBeya settings. DNS propagation can take up to 48 hours, but typically completes within minutes.
SSL Certificate
ProBeya automatically provisions and renews an SSL certificate for your custom domain via Let’s Encrypt. No action needed.
Locale-Suffixed Subdomains
ProBeya supports language selection directly in the subdomain URL by appending a hyphen and a two-letter locale code after the organization slug:
https://{slug}-{locale}.probeya.com
How It Works
| URL | Tenant | Language |
|---|---|---|
acme.probeya.com | acme | User’s browser preference |
acme-fr.probeya.com | acme | French |
acme-de.probeya.com | acme | German |
acme-nl.probeya.com | acme | Dutch |
acme-es.probeya.com | acme | Spanish |
acme-it.probeya.com | acme | Italian |
acme-en.probeya.com | acme | English |
The locale suffix is always the last hyphen-separated segment. Organization slugs containing hyphens work naturally:
| URL | Tenant | Language |
|---|---|---|
my-company.probeya.com | my-company | Browser preference |
my-company-fr.probeya.com | my-company | French |
Supported Locales
ProBeya supports thirteen languages: en (English), fr (French), nl (Dutch), de (German), it (Italian), es (Spanish), pt (Portuguese), ru (Russian), ar (Arabic, RTL), id (Indonesian), zh (Chinese), ja (Japanese), ko (Korean).
Locale Priority
When a locale-suffixed URL is used, it takes highest priority over all other locale settings:
- Subdomain suffix —
demo-fr.probeya.comforces French - NEXT_LOCALE cookie — set by the user’s language preference in the app
- Browser Accept-Language header — detected from the user’s browser
- Default — English
The subdomain locale also updates the user’s locale cookie, so subsequent visits to the plain subdomain (e.g., demo.probeya.com) will retain the language choice.
Share locale-suffixed URLs with international teams so each person lands directly in their preferred language — no manual language switching needed.
Multi-Subdomain API Access
All API requests are scoped to the organization identified by the subdomain:
# Access ACME organization's data
curl https://acme.probeya.com/api/v1/boards \
-H "Authorization: Bearer YOUR_TOKEN"
# Access Different organization's data
curl https://other-org.probeya.com/api/v1/boards \
-H "Authorization: Bearer DIFFERENT_TOKEN"
API tokens are scoped to a single organization. A token created in acme.probeya.com cannot be used to access other-org.probeya.com.
Subdomain Security
- All subdomains are served over HTTPS with automatic certificate management
- Cookies are scoped to the specific subdomain — no cross-tenant cookie leakage
- CORS policies are enforced per-subdomain
- Rate limiting is applied per-subdomain to prevent abuse
Allowed Subdomains
The following subdomains are reserved and cannot be used:
www, app, api, admin, status, docs, help, support, blog, mail, smtp, ftp, ns1, ns2, cdn, assets, static, staging, dev, test
Was this page helpful?