Workspaces, Subdomains & Custom Domains

Workspaces in ET Ducky

A workspace is your team's tenant on ET Ducky: the outer container that everything else lives inside. One workspace owns one URL (a subdomain on etducky.com like acme.etducky.com) and can hold one or many Clerk organizations. Agents, alerts, scripts, tickets, integrations, and team members all belong to organizations; organizations belong to a workspace.

If you're a single team monitoring your own infrastructure, you'll typically have one workspace with one organization inside it. If you're an MSP managing multiple clients, you'll have one workspace with one organization per client.

ConceptWhat it isExamples
WorkspaceYour team's tenant. Owns the URL, the seat pool, and the workspace member list.acme.etducky.com
OrganizationAn isolation boundary inside the workspace. Owns agents, alerts, scripts, tickets, and integrations.“Acme Internal”, “Client A”, “Client B”
SubdomainThe DNS hostname that routes to your workspace. The slug is editable; the binding is permanent.acme in acme.etducky.com

Your Workspace

Every ET Ducky team gets a dedicated workspace at a subdomain on etducky.com. The workspace is created automatically the first time you sign up: you never have to ask, and you can start using the dashboard immediately.

What happens at sign-up

The moment your Clerk account is created, ET Ducky provisions:

  • A workspace with a random readable slug like etd-x7q3p2.etducky.com
  • A default Clerk organization inside the workspace, with you as its owner
  • Owner membership for you on the new workspace

You'll land on your dashboard at the auto-generated URL with everything wired up. No claim wizard, no DNS setup, no waiting.

Signing in for the first time at etducky.com

If you sign in at the apex URL (etducky.com) rather than a workspace subdomain, ET Ducky checks how many workspaces you belong to and routes you accordingly:

  • Zero workspaces: the Claim your subdomain modal opens. Pick a slug, click claim, and we provision your workspace and a default organization, then redirect you to <slug>.etducky.com.
  • One workspace: you're redirected straight to it.
  • Two or more workspaces: the Choose your workspace picker opens with one row per workspace and your role in each, so you can decide which one to enter.

Personalizing your URL

Default slugs are fine for getting started, but most teams want something memorable. To rename your workspace, go to Settings → Workspace in the dashboard. Renaming is instant and preserves every existing org binding, agent, alert rule, integration, and ticket: only the URL changes.

After a rename, the old subdomain continues to work as a grace-period alias for a window so any in-flight bookmarks, invite links, and agent connections keep functioning while your team migrates. Agents pick up the new URL automatically through their existing SSE connection: you don't need to reinstall or reconfigure them.

What you do NOT need to do

  • No DNS changes on your end. The subdomain resolves automatically. Nothing to configure with your domain registrar.
  • No certificate request. The HTTPS cert covering *.etducky.com is already provisioned. Your URL is TLS-secured immediately.
  • No firewall rule. Your team accesses the dashboard from anywhere: nothing changes on your network.

Slug rules (when renaming)

  • 3–63 characters, lowercase letters, digits, and hyphens only
  • Cannot start or end with a hyphen
  • Cannot match reserved names (www, admin, api, status, mail, etc.)
  • Slug is unique across ET Ducky: if your preferred slug is taken, the rename will reject it and you can try another

Picking a good slug

Use your company name or a recognisable abbreviation. The slug appears in URLs your team and end-users will see, and it's part of your invite links. Short, memorable slugs are best. URLs you've already shared (invite links, agent installer URLs, integrations) will need to be reissued after a rename, since the host portion changes.

Inviting Team Members

Once your subdomain exists, your invite links route to it automatically:

https://acme.etducky.com/join?token=<invite-token>

Send the link to a colleague, they sign in with Clerk, and they're added to your subdomain with the role you specified. Invite links expire after 14 days by default, with optional shorter expirations for sensitive roles.

Verified Domains

Verifying a domain you own, for example acme.com, proves to ET Ducky that your workspace controls it. A verified domain lets you claim a matching workspace slug, route sign-ins from that domain through single sign-on (see below), show a verified mark on sign-ups from that domain, and is the base for a custom dashboard domain such as rmm.acme.com (see Custom domain for the dashboard). Verifying a domain does not by itself open the dashboard at that domain.

Verify a domain

  1. Go to Configuration → Workspace → Verified Domains and click Add Domain. ET Ducky shows a TXT record.
  2. In your DNS provider, add a TXT record named _etducky-verify under the domain (for acme.com, the full name is _etducky-verify.acme.com) with the value ET Ducky showed, which has the form etducky-verify-<your slug>=<token>.
  3. Wait a few minutes for DNS to update, then click Verify.

The value names your workspace slug, so a record copied from another workspace does not verify yours. Removing a domain releases it; another workspace can then add it.

Workspace Branding (White-Label Add-On)

A workspace that has the white-label add-on can show its own product name, logo, accent color and support contact in place of ET Ducky's on its workspace address, for example acme.etducky.com. A “Powered by ET Ducky” line stays under the product name.

Buying the add-on

White-label branding costs $19 a month per workspace. Two options can be added to it: a custom domain for the dashboard and sign-in, such as rmm.acme.com, for $25 a month more (see Custom domain for the dashboard), and removal of the “Powered by ET Ducky” line for $10 a month more (see Removing the Powered by line). The workspace address itself, acme.etducky.com, costs nothing extra.

The add-ons are for workspaces on a paid ET Ducky plan: a query subscription or purchased agent seats, including plans with agent seats only. Free and Bring Your Own Key plans cannot buy them; both purchase cards say so, and checkout refuses until the organization has a paid plan.

  1. On your workspace address, go to Configuration → Subscriptions → White-label branding, or Configuration → Workspace → Branding.
  2. Tick the options you want and click Continue to checkout. Payment is handled by Stripe.
  3. After payment the Branding card opens again and the form can be used. If it still says branding needs the white-label add-on, reload the page after a minute.

A workspace that pays online changes its options on either card with Update add-ons; the change is prorated. Cancelling the subscription in the billing portal ends the add-on when Stripe ends the subscription, and the workspace then shows ET Ducky's branding again. If a payment fails, the branding stays while Stripe retries the payment, and ends if Stripe cancels the subscription or marks it unpaid. Removing an option never needs a paid plan. Only workspace owners and admins can buy or change the add-on.

What changes on the workspace address

  • The browser tab title, the name and logo in the navigation bar, and the browser tab icon.
  • The accent color replaces ET Ducky's colors throughout the dashboard: buttons, links, active tabs, highlights, the product name and focus rings. Status colors (success, warning, danger, information) and chart colors stay as they are. When the accent is too light for white text, buttons use a darker shade of it so their text stays readable.
  • Page text in the dashboard that names the product uses your product name. Links to ET Ducky's documentation, legal text and the “Powered by ET Ducky” line keep ET Ducky's name.
  • The sign-in and sign-up windows show your logo and accent color. Their title line, which names the sign-in service's application, is hidden. The windows do not show your product name.
  • A “Powered by ET Ducky” line under your product name in the navigation bar, unless the workspace pays for its removal (see Removing the Powered by line). The Branding card shows a preview of the navigation bar with the line where it appears.

What changes in notifications

Alert emails and automation emails from the workspace's organizations come from “your product name Alerts”. The subject line is not branded: it is the email channel's own subject, with {rule_name}, {severity} and {agent_name} filled in, or the alert's severity and rule name. Replies go to your support email when you set one. The email ends with your product name, your support contact and a “Powered by ET Ducky” line, unless the workspace pays for its removal. The sending address stays ET Ducky's, so the email passes the receiving server's checks. Push notifications without a rule name and Slack messages without a channel name of their own use your product name. A change reaches notifications within about a minute.

What changes on devices

Agents from version 2.8.5.8 show your product name in the dialogs they open for the people at the device, and your support email and support link where a dialog shows a support contact. A “Powered by ET Ducky” line appears where the dialog has room, unless the workspace pays for its removal.

  • Windows: the Request Support window, the restart prompt after updates and the restart warning, the Isolation Removal Request window and the Lift Network Isolation window.
  • Linux: the Request Support dialogs, the Isolation Removal Request prompt, and the restart message that signed-in users see after updates.

Shortcuts, from the first agent version released after 2.8.5.8:

  • Windows: in the Start menu's “ET Ducky Agent” folder and on the public desktop, “Request Support” keeps its name and “ET Ducky Documentation” becomes “your product name Documentation”; both show your logo. Installers from that version put the desktop shortcuts on the public desktop; copies an older installer put on one user's own desktop keep ET Ducky's name and icon. After an agent update or reinstall the agent applies the names and logo again within a few minutes.
  • Linux: the “Request Support” application menu entry shows your logo when the logo is a PNG or JPEG image (a WebP logo keeps ET Ducky's icon). There is no Documentation entry on Linux.

A change to the branding reaches each device at its next heartbeat, usually within two minutes, with no reinstall. Removing the branding, or the end of the add-on, returns the dialogs to ET Ducky's text the same way. An agent keeps the branding in its protected state folder, so its dialogs are branded right after a restart; an agent that has not yet received the branding shows ET Ducky until its first heartbeat. The isolation dialogs show your support email and link in place of ET Ducky's phone number and address, or ask the user to contact their IT support when you set neither.

What stays ET Ducky

  • The workspace address. It is still a subdomain of etducky.com, unless the workspace also has the custom domain option (see Custom domain for the dashboard). On every workspace address, branded or not, the address itself opens the Agents page, or, when you are signed out, a sign-in page with the sign-in window open (on a custom domain, its Sign in button takes you to the workspace address), instead of the ET Ducky home page. The Home link in the navigation bar opens the Agents page too. Link previews of the address in chat and email apps still name ET Ducky.
  • Verification codes and sign-in link emails sent by the sign-in service, and the Google and Microsoft sign-in consent screens.
  • On devices: the agent installer, the service and package names, the install folders, the Start menu folder name, the Reconfigure shortcut, the ET Ducky Desktop app's own shortcut, and the Documentation and Automation recorders.
  • The ET Ducky website at etducky.com, including the documentation and pricing pages.

The dashboard does not show the support email and support link. Agent dialogs on devices do.

Setting up branding

  1. Open the dashboard on your workspace address and go to Configuration → Workspace → Branding.
  2. Enter a product name of up to 60 characters, without < or >. The accent color is optional and is a hex color such as #1a73e8. The support link and the company website must start with https://.
  3. Choose a logo file if you want one. It must be a PNG, JPEG or WebP image of up to 256 KB.
  4. To start from your website instead, enter its address in Company website and click Fill from website. ET Ducky reads the page and fills in the name, the accent color, the support link and a square logo where the page names them (its site name or title, its theme color, and its touch or app icons). Check every field before you save. Clicking Fill from website again replaces what the last fill filled in, including a support link or logo it found, and clears them when the new site has none; a support link you typed or saved stays. Nothing is saved until you click Save branding. The website must use https on the standard port; a workspace can use this 10 times an hour.
  5. Click Save branding, then reload the page.

Review by ET Ducky

ET Ducky reviews a new product name, logo, support email, support link or company website before the workspace shows it. Until the change is approved, the workspace keeps its last approved branding, or ET Ducky's branding if none was approved yet. The Branding card says that a change is waiting for review, and shows ET Ducky's note if a change was not approved. A change to the accent color alone applies at once. The logo is also the browser tab icon, so a new icon is reviewed with the logo.

The review compares the support email and support link with the company website, and checks whether the website's domain is one of the workspace's verified domains (see Verified Domains above). Verifying the domain first, and using a support address on that domain, makes the review straightforward.

Removing the Powered by line

The “Powered by ET Ducky” line appears in three places: under your product name in the navigation bar of the workspace address (it stays visible behind the sign-in window, which does not show it itself), at the end of alert and automation emails, and in the agent dialogs on devices where the dialog has room, including the Isolation Removal Request prompt. With the removal option it disappears from all three. The line is removed only while your approved branding names a support email or support link. Without one, the line stays and the Branding card says why.

Only workspace owners and admins can save or remove branding. Other users see an approved change within about a minute. Use ET Ducky branding removes the saved branding. When a workspace no longer has the add-on, its saved branding is kept and is not shown.

Custom Domain for the Dashboard (White-Label Add-On)

With the custom domain option of the white-label add-on ($25 a month on top of branding), the workspace's dashboard opens at a host name under your own domain, for example rmm.acme.com, with your branding. Your workspace address, acme.etducky.com, keeps working and costs nothing extra.

Setting it up

  1. Buy the custom domain option on the Branding card (see Workspace Branding).
  2. Verify the domain the host belongs to, for example acme.com (see Verified Domains above).
  3. On the Branding card, enter the host in Custom domain for the dashboard and click Request custom domain. The host must be under a verified domain, and it cannot be the domain itself, because the domain's own name cannot carry the records below.
  4. ET Ducky sets up the sign-in service and the certificate for the host and emails you the DNS records to add: a CNAME for the host itself, and a CNAME for clerk. in front of the host (for example clerk.rmm.acme.com), which the sign-in service uses. If your DNS is on Cloudflare, set both records to DNS only. DNS changes can take up to 48 hours to reach everyone.
  5. When the records work, ET Ducky marks the domain active and the Branding card says it is live.

How sign-in works on the custom domain

  • Signing in and signing up happen on your workspace address, acme.etducky.com, which shows your branding. After signing in, the browser returns to the custom domain.
  • Signing out on either address signs out of both.
  • The sign-in service does not recommend passkeys across two domains; use another sign-in method on the custom domain.
  • Agents, the agent installers and the ET Ducky website keep using ET Ducky's addresses.

Removing the custom domain on the Branding card stops it being used for the workspace. Delete the DNS records afterwards.

Single Sign-On (SSO)

Once you've verified a domain, you can route signins from that domain through your existing identity provider. ET Ducky supports SSO via Clerk's enterprise authentication, with a one-click setup for Microsoft 365 / Microsoft Entra. Traditional SAML for Okta, OneLogin, JumpCloud, and other custom IdPs is on the roadmap.

What "Enable Microsoft SSO" does

When you toggle Enable Microsoft SSO on a verified domain, three things happen:

  • The domain is added to ET Ducky's Clerk enterprise SSO connection.
  • Future signins from @yourdomain.com email addresses are auto-routed to Microsoft instead of asking for a password: your IT keeps controlling who has access via Entra ID.
  • The first user from your tenant to sign in triggers a one-time admin-consent prompt in your Microsoft tenant ("Allow ET Ducky to read user profile and email"). Once your tenant admin clicks Allow, subsequent users sign in transparently.

Prerequisites

  • The domain must be verified (TXT record + Check verification) before SSO can be enabled. Verification establishes that you control the domain before you wire it to your IdP.
  • You must have a Microsoft Entra ID tenant attached to your Microsoft 365 / Azure account. Personal Microsoft accounts (@outlook.com, @hotmail.com) don't have a tenant and can't be used as the SSO authority.
  • Your Microsoft tenant admin needs Global Administrator or Application Administrator role to consent to the app the first time it's used.

Enabling SSO

  1. Verify your domain first (see Verified Domains above).
  2. Go to Settings → Verified Domains.
  3. Click Enable Microsoft SSO on the row for your verified domain.
  4. Read the confirmation prompt and click OK.
  5. The row now shows an "SSO: Microsoft" badge. Future @yourdomain.com signins are routed through Microsoft.

What happens on first signin from a domain with SSO enabled

The first employee from your domain signs in, is redirected to Microsoft's signin page, and authenticates against your Microsoft tenant using your password rules, MFA, and conditional-access policies. If they're the first user from your tenant to reach ET Ducky, Microsoft shows an admin-consent screen ("ET Ducky wants to read user profile, email"). The signing-in user clicks Allow if they have the right role, or forwards the screen to their IT admin. Once consent is granted, all subsequent @yourdomain.com users sign in transparently.

Users from other email domains in your workspace (for example a @gmail.com external contractor) continue to sign in normally with their existing method. SSO only applies to the domains where you've explicitly enabled it.

How user isolation works

ET Ducky uses a single multi-tenant Microsoft app under the hood, but each customer's users authenticate against their own Microsoft tenant: never against ET Ducky's tenant. If your IT disables an employee in Microsoft Entra, their ET Ducky access stops on their next signin. ET Ducky doesn't store passwords for SSO users; Microsoft does. Different ET Ducky customers using SSO are completely isolated from each other: the shared Microsoft app is only an authentication intermediary, never a data path.

Disabling SSO

Toggle Disable SSO on the verified domain row. Future signins fall back to whatever auth method they had before (password, Google, etc.). Sessions that were already signed in via SSO stay valid until they expire naturally (typically within a week); to force immediate re-authentication, contact support.

Custom SAML providers

If your IdP isn't Microsoft 365 / Entra ID (Okta, OneLogin, JumpCloud, or a custom SAML provider), the Microsoft-EASIE one-click flow won't fit. Custom SAML support is on the roadmap and will surface as an "Advanced: Configure SAML manually" option on the same verified-domain row. Contact support if you need this today; we can configure the Clerk-side connection manually while the self-serve UI is in development.

Pending Join Requests

When someone signs up with an email at a non-public domain that's already claimed by another ET Ducky workspace, ET Ducky doesn't create a parallel workspace for them. Instead, it surfaces a Pending join request banner at the top of their dashboard pointing at the existing workspace, with options to Withdraw request or Hide for now. The original workspace owner sees the request on their Team page and can approve or reject it.

  • Approved: the user is added as a workspace member with the default role (member). They can switch to that workspace from their org picker.
  • Rejected or withdrawn: the user stays on their personal auto-bootstrapped workspace.
  • Expired: requests expire after 30 days if no decision is made.

If SSO is enabled for the email's domain on the claimant's workspace, the request is skipped entirely: Clerk's SSO flow handles membership automatically during signin and no manual approval is needed.

Free-email signups (gmail.com, outlook.com, proton.me, etc.) always get a fresh personal workspace; they never trigger a join request because there's no notion of a "company workspace" for a free-email domain.

Multiple Organizations in One Workspace

If your team is an MSP managing multiple client organizations, all of those orgs live in your single workspace. The dashboard's organization picker (top-left) lets you switch between them; the URL stays the same (acme.etducky.com), but the API requests carry an X-Clerk-Org-Id header that scopes everything to whichever org you've selected.

A single login at acme.etducky.com gives you access to every organization in the workspace: no logging out and back in.

Workspace membership cascades to every org

When someone is added to your workspace (through a workspace invite, by accepting an invite at the workspace URL, or by you binding an existing organization to the workspace) ET Ducky automatically grants them membership in every Clerk organization that already lives in the workspace. New organizations created later in the workspace also receive every existing workspace member as a member of that new org. The result is that “workspace member” and “has access to all orgs in the workspace” are the same thing in practice; you don't have to invite people to each org individually.

If you need someone to see only a specific organization (for example, a customer's IT contact who should see their fleet but not your other clients'), invite them directly to that organization at its own subdomain rather than to your workspace. Workspace-level invites are the right tool for your own team and partners; per-org invites are the right tool for client-facing access.

Org dropdowns only show this workspace

Every organization picker in the dashboard (on the Dashboard, Agents, Team, Alerts, Reports, Tickets, Integrations, Automations, and KB pages) lists only the organizations that belong to the current workspace. If you're a member of multiple workspaces, you won't accidentally see an org from a different workspace in the dropdown, and switching orgs can never load data from outside the workspace you're in. The list is sourced from the API directly (rather than from your browser's Clerk session), so it stays consistent no matter which workspace you switched from last.

How data is partitioned between orgs

Each Clerk organization inside the workspace is its own isolated tenant. Switching the active org in the picker re-scopes every page in the dashboard:

  • Agents are scoped per Clerk org. The Agents page only shows agents installed under the currently-active org. Switching orgs gives you a different fleet view.
  • Alert rules, automations, scripts, tickets, and integrations are all per-org. A script you create under Acme Org A is invisible from Acme Org B, even though both are in the same workspace.
  • Live sessions and remote desktop can only target agents in the active org. To remote into a machine in a different client's fleet, switch to that client's org first.
  • Subscriptions and billing roll up at the workspace level (your team's owner pays for all seats across all client orgs); usage attribution per client org is visible on the Billing page.

This architecture deliberately keeps client data separated. If you'd rather have one shared fleet across multiple internal teams, put them all in a single Clerk org under the workspace rather than separate orgs.

Active org auto-selection

If only one Clerk org exists in the workspace, it's selected automatically on every login. If several do, the dashboard remembers the org you last used in this workspace. Need to switch on every visit? Pick from the org picker each time: selection persists per browser tab.

Removing someone removes them from the whole workspace

Membership is scoped to the workspace, so removing a person from your team removes them from the workspace and from every organization inside it, not just the org you removed them from. This is the flip side of the cascade above: one action grants access everywhere, and one action takes it away everywhere.

If they have the dashboard open at the time, their next action returns an error rather than silently failing, and the app sends them back to a page they can still reach. Reopening the workspace URL afterwards takes them to the sign-in page for a workspace they no longer belong to. Nothing they created is deleted: agents, tickets, scripts, and history all stay with the organization.

To restore their access, re-invite them to the workspace; the cascade puts them back into every org. To give someone access to one organization only, invite them to that organization directly instead of to the workspace.

Released Workspaces and How to Get One Back

Workspace URLs are a shared, finite namespace, so a workspace that never converts to a paid plan eventually gives its name back. This is the normal end of a trial that doesn't convert, not a penalty, and it does not delete anything.

When a workspace is released

  • Never subscribed: 30 days after sign-up.
  • Trialed and didn't convert: 30 days after the trial ends. Because that clock starts at the end of the trial rather than at sign-up, a trial gives you more total runway, not less.

What release actually does

The workspace's URL is changed to a random internal name, freeing your original slug for anyone to register, including a colleague at your own company. The workspace stops appearing in your workspace picker at etducky.com, and its team memberships are removed. Your original name is kept on the record so support can see what it was.

Ninety days after that, the workspace and its organizations are marked inactive. That is still a visibility change, not a teardown: agents, events, tickets, scripts, and history are all left in place.

Getting it back

Start a paid plan, then sign in at etducky.com. If you try to create a new workspace while a released one is on your account, ET Ducky recognizes the situation and offers to restore the old one instead of refusing:

  1. A dialog appears naming the workspace you lost: “Your workspace acme is still here”: and explains that nothing was deleted.
  2. Click Restore my workspace. Your original URL comes back if it is still free, along with your organizations, your owner membership, and your fleet.
  3. If somebody else registered your original name in the meantime, the workspace still comes back: under a different name, which you can change later under Configuration. Losing the name is the one thing release can cost you, which is why the clock matters.

Restoring requires an active subscription. Without one you'll see a prompt to choose a plan; the workspace stays exactly where it is in the meantime, so there's no rush to decide.

If you'd rather have your original name than a restored workspace, for instance you've since built a new one you prefer, contact support rather than restoring; they can see both records.

Troubleshooting

"Workspace not found" / "Subdomain not found"

Double-check the slug spelling. If you just registered, give DNS a couple of minutes to propagate.

If the URL used to work and now doesn't, the workspace was most likely released because it never moved to a paid plan: see Released Workspaces. You can restore it yourself once you have an active plan; you don't need support for this. If someone else has since registered the name, that page explains what happens.

A workspace deactivated for inactivity is a different case: contact support, which can reactivate it for up to 90 days after deactivation.

"Active organization is required"

You're hitting a workspace URL but Clerk hasn't set an active organization. Click the org picker in the top-left and select one. If only one organization exists in the workspace, this is set automatically; if you've just been removed from your last org in the workspace, contact your workspace owner. The dashboard auto-recovers from a stale active org by intersecting your Clerk memberships with the current workspace's org list and selecting a valid one.

"You don't belong to any organization in this workspace"

You signed in at a workspace URL where you're a workspace member but have no current Clerk org membership inside it: usually because every org in the workspace was created before you joined, or because all of your org memberships in this workspace were removed. The membership cascade fixes this automatically when new orgs are created or when you're re-invited; in the interim, ask a workspace admin to add you to one of the existing organizations or to re-invite you.

This is distinct from being removed from the workspace. If a workspace admin removed you from the team, you are no longer a workspace member at all and you'll be sent to sign-in rather than shown this message: the fix there is a fresh workspace invite, not an org invite.

Domain verification fails

Most common cause: DNS hasn't propagated yet. Run dig +short TXT _etducky-verify.acme.com from your terminal: the TXT value should match what ET Ducky asked for. If it returns nothing, your DNS update hasn't taken effect; wait or check that you saved the change in your DNS dashboard.

Second most common cause: your domain is on Cloudflare with the proxy enabled (orange cloud). Cloudflare doesn't expose TXT records the same way to external lookups. Set the verification TXT record to DNS-only (gray cloud) until verification succeeds.

The custom domain shows a "your connection is not private" error

Check that you're opening the host exactly as requested on the Branding card. Until the Branding card says the custom domain is live, its certificate may not exist yet. If it says live and the error persists, check that both CNAME records are DNS only, then contact support.