626455b534
## Summary Two things, both fallout from #20360: 1. Rename the `Members → Access` tab to `Members → Invite`. The previous label leaned security-flavored; "Invite" reads as the verb users come here to do. 2. Fix the `signup_invite_email` Playwright test (failing on main, e.g. https://github.com/twentyhq/twenty/actions/runs/25671161586/job/75356474079). The invite-link button moved off the default Team tab when the Members page got tabbed; the test was looking for it on the wrong tab. ## Rename details - File: `SettingsWorkspaceMembersAccessTab.tsx` → `SettingsWorkspaceMembersInviteTab.tsx` (single git rename, ~99% similarity) - Exported component: `SettingsWorkspaceMembersAccessTab` → `SettingsWorkspaceMembersInviteTab` - Tab id (and URL hash): `access` → `invite` - Tab title: `Access` → `Invite` - Icon: `IconKey` → `IconUserPlus` - Doc breadcrumbs (3 files): `Members → Access` → `Members → Invite` ## E2E fix `MembersSection` (Page Object Model) now has an `inviteTab` locator (via `getByTestId('tab-invite')`) and a `goToInviteTab()` helper. Both `copyInviteLink` and `sendInviteEmail` click the Invite tab first, so they work regardless of which tab the page lands on initially. Idempotent if already there. ## Test plan - [x] CI green (e2e test + lint + typecheck + format) - Lingui `.po` files will pick up the new source paths on the next translation pass — not touched here. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
52 lines
1.7 KiB
Plaintext
52 lines
1.7 KiB
Plaintext
---
|
|
title: Domain Settings
|
|
description: Configure workspace domain, approved access domains, and public domains.
|
|
---
|
|
|
|
Domain settings live in three places, depending on what you're configuring.
|
|
|
|
## Workspace Domain
|
|
|
|
Configure under **Settings → General → Workspace Domain**.
|
|
|
|
Edit your subdomain name or set a custom domain for your workspace.
|
|
|
|
### Customize Domain
|
|
1. Click **Customize Domain**
|
|
2. Edit your subdomain (e.g., `yourcompany.twenty.com`)
|
|
3. Or set up a custom domain (e.g., `crm.yourcompany.com`)
|
|
|
|
For custom domains, you'll need to configure DNS settings with your domain provider.
|
|
|
|
## Approved Domains
|
|
|
|
Configure under **Settings → Members → Invite**.
|
|
|
|
Anyone with an email address at these domains is allowed to sign up for this workspace automatically.
|
|
|
|
### Add Approved Access Domain
|
|
1. Click **Add Approved Access Domain**
|
|
2. Enter your company domain (e.g., `yourcompany.com`)
|
|
3. Save
|
|
|
|
Once configured, anyone with an email address at that domain can join your workspace without needing a direct invitation.
|
|
|
|
<Note>
|
|
This is useful for allowing your entire team to self-register while keeping the workspace restricted to your organization.
|
|
</Note>
|
|
|
|
## Public Domains
|
|
|
|
Configure under **Settings → Apps → Developer**.
|
|
|
|
Provision a complete and secure hosting environment on these domains. A public domain can be bound to a specific app — when bound, only that app's HTTP-routed logic functions are reachable on the domain. Leave the binding empty to expose all workspace HTTP routes.
|
|
|
|
### Add Public Domain
|
|
1. Click **Add Public Domain**
|
|
2. Enter the domain you want to use
|
|
3. Optionally bind it to an app
|
|
4. Configure DNS settings as instructed
|
|
5. Verify the domain
|
|
|
|
SSL certificates are automatically provisioned for public domains.
|