Eduard GertandClaude Opus 5 4df2518616 Add Sign-in Domains page (#970)
* Add Sign-in Domains page

Documents how an email domain is matched to an account: adding a domain,
proving ownership with a DNS TXT record, and what changes for users once it is
verified.

Two points the page is careful about, because both are easy to assume wrongly:

- Verifying a domain decides where *new* users land. It does not move users who
  already have an account of their own, so domains want adding before a team is
  onboarded rather than after.
- A verified sign-in domain is not an SSO domain. Routing a domain to an
  identity provider is a separate step on the integration, which is what lets
  one domain sign in through SSO while another uses Google or a social login.

The four screenshots it references are not in this commit and need to be added
before merge:

  public/docs-static/img/manage/team/sign-in-domains/
    sign-in-domains-settings.png          the Sign-in Domains tab in Settings
    sign-in-domains-pending.png           a newly added domain, Pending
    sign-in-domains-dns-verification.png  the TXT record dialog
    sign-in-domains-login.png             the login page

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Tighten the Sign-in Domains page

Switches the examples to company.com / company.net, drops the step-by-step
walkthrough of how matching works, and trims the instructions down to what a
reader actually needs to do. The prose and the callouts carry the page now.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Trim the Sign-in Domains page further

Parallel section titles (Add / Verify / Remove Domain), drops the
"What Changes for Your Users" and "Things Worth Knowing" sections, and cuts
the availability note and the SSO note back to one line each.

The warning now says to add domains before onboarding a team from another
domain, which is the case it actually matters for.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Move Sign-in Domains under Settings, and lead with the two domains

Sign-in Domains is a Settings tab in the dashboard, not part of Team, so the
page moves to /manage/settings/sign-in-domains and sits in the Settings nav
after Authentication, mirroring the dashboard's own tab order. Screenshots move
with it to img/manage/settings/sign-in-domains/.

The intro also led with jane@company.com, which would already have matched the
primary domain and so did not show the problem at all. It now establishes
company.com as the account's own domain and company.net as the second one, and
the colleague who needs it is jane@company.net.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Lead with what sign-in domains are for

Retitles the page "Allow Users from Other Domains to Join Your Account", which
is the job it does, and opens with the behaviour rather than with the account's
own domain: users on one business email domain are already joined into one
account, and most businesses have more than one domain -- another location, a
country domain, a second brand -- whose users are not.

Also documents the email route the verification dialog offers for anyone
without DNS access, and matches the dialog's own wording (Verify on the row,
then Start Verification).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Sharpen the intro and drop the primary-domain aside

- The colleague on another domain is not recognized unless invited by hand, so
  the intro says so and links to the invite page.
- "With sign-in domains you prove ownership of those domains, and everyone
  across your organization joins the same account."
- Drops the paragraph about company.com staying the primary domain. Remove
  Domain named that term without defining it afterwards, so it now says "the
  domain your account signed up with" instead.
- Drops the detail about the retry interval widening; that it keeps checking is
  the part a reader needs.
- US spelling, matching the rest of the docs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Shorten the one-account-per-domain note

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Drop the SSO section, and nest the page under Authentication

The "Sign-in Domains and SSO" section read as confusing rather than
clarifying, so it goes along with its recap bullet. The constraint a reader
actually meets survives in Remove Domain: a domain an SSO integration uses
cannot be deleted until it is detached there.

The page also moves under the Authentication group in the sidebar, next to
Peer Session Expiration and Multi-Factor Authentication.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Follow the dashboard: Sign-in Domains lives under Authentication

The dashboard no longer gives sign-in domains a tab of their own, so the
instruction now sends the reader to Settings > Authentication and the section
within it. The screenshot is renamed to authentication-tab.png to match what
it has to show.

Also spells out that joining happens automatically without direct invites,
and drops the same point from the opening paragraph where it was now said
twice.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Move the page under Single Sign-On

/manage/team/single-sign-on/sign-in-domains, nested under Single Sign-On in
the Team section rather than sitting under Settings. Screenshots move with it
to img/manage/team/single-sign-on/sign-in-domains/.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Put the page at manage/team/sign-in-domains

A sibling of Single Sign-On in the Team section, listed after it, rather than
nested inside it or under Settings. Screenshots follow to
img/manage/team/sign-in-domains/.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Fix wording and a stale example domain

The DNS instruction still named www.company.net after the example moved to
company.co.uk, which is the one that actually misleads: that sentence is
telling people where to put the record.

Also a "usees" typo, a link with no object ("unless you invite manually"), a
missing comma after "By default", "as you" where the comparison is to your
domain, "E.g." opening a sentence, and "another one" where it means another
account.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Drop the authentication clause from the recap

It summarised the SSO section, which is gone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Add the Sign-in Domains screenshots

- authentication-tab.png: the section under Authentication, with two domains
  pending and two verified, which is what the page describes
- dns-verification.png: the Verify Domain Ownership dialog
- login.png: the login page

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Point domain verification help at NetBird Support

Replace the support@netbird.io mailto links with links to the support
page, and tell users with an account they were not aware of to reach out
so the team can verify their identity and point them to its admin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-28 10:19:37 +02:00
2024-03-08 16:27:55 +01:00
2026-09-28 10:19:37 +02:00
2026-09-28 10:19:37 +02:00
2023-05-25 11:32:38 +02:00
2026-07-27 11:08:52 +02:00
2026-07-27 11:08:52 +02:00
2025-11-21 11:24:17 +01:00

The NetBird documentation

This repository contains assets required to build the documentation website for NetBird. It is built using Next.js with MDX support, a modern React framework for building static and dynamic websites.

We're glad that you want to contribute!

Requirements

  • node 16
  • npm 8+

Installation

$ npm install

Local Development

$ npm run dev

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Contributing to the docs

You can click the Fork button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.

Once your pull request is created, a NetBird reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, it is your responsibility to modify your pull request to address the feedback that has been provided to you by the NetBird reviewer.

Also, note that you may end up having more than one NetBird reviewer provide you feedback or you may end up getting feedback from a NetBird reviewer that is different than the one initially assigned to provide you feedback.

Furthermore, in some cases, one of your reviewers might ask for a technical review from a NetBird author when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.

Code of conduct

Participation in the NetBird community is governed by the NetBirds' Code of Conduct.

Components and Use

This documentation uses several custom MDX components. Here's a guide to the most commonly used components:

Alert Components

Use these components to highlight important information:

Note

Displays informational content with an orange theme:

import {Note} from "@/components/mdx"

<Note>
    NetBird is an **[open-source](https://github.com/netbirdio/netbird)** project and can be self-hosted.
    See a comparison between the self-hosted and cloud-hosted versions [here](/selfhosted/self-hosted-vs-cloud-netbird).
</Note>

Warning

Displays warning content with a red theme:

import {Warning} from "@/components/mdx"

<Warning>
    The API is still in Beta state so some errors might not be handled properly yet.
</Warning>

Success

Displays success messages with a green theme:

import {Success} from "@/components/mdx"

<Success>
    Your configuration has been successfully applied.
</Success>

Tiles Component

Displays a grid of clickable cards with hover effects. Perfect for listing related resources or guides:

import {Tiles} from "@/components/Tiles"

<Tiles 
  title="About NetBird" 
  id="about-netbird" 
  items={[
    {
      href: '/about-netbird/how-netbird-works',
      name: 'How NetBird Works',
      description: 'Learn about NetBird concepts, architecture, protocols, and how it creates secure networks.',
    },
    {
      href: '/about-netbird/netbird-vs-traditional-vpn',
      name: 'NetBird vs. Traditional VPN',
      description: 'Discover how NetBird compares to traditional VPNs and understand the advantages of Zero Trust networking.',
    },
  ]} 
/>

Props:

  • title (string, required): The heading title for the tiles section
  • id (string, optional): Optional id for the heading anchor
  • items (array, required): Array of objects with href, name, and description
  • buttonText (string, optional): Button text (defaults to "Read more" - currently unused as cards are fully clickable)

YouTube Component

Embeds YouTube videos with customizable parameters:

import {YouTube} from "@/components/YouTube"

<YouTube videoId="CFa7SY4Up9k" />

// With custom parameters
<YouTube 
  videoId="CFa7SY4Up9k" 
  title="Video Title"
  start={175}
  color="white"
  modestbranding={1}
  rel={1}
/>

// Or use a URL instead of videoId
<YouTube url="https://www.youtube.com/watch?v=CFa7SY4Up9k" />

Props:

  • videoId (string): YouTube video ID
  • url (string): YouTube URL (alternative to videoId)
  • title (string, optional): Video title
  • start (number, optional): Start time in seconds
  • color (string, optional): Progress bar color - 'white' or 'red' (default: 'white')
  • modestbranding (number, optional): Reduces YouTube branding - 0 or 1 (default: 1)
  • controls (number, optional): Show/hide controls - 0, 1, or 2 (default: 1)
  • rel (number, optional): Show related videos - 0 or 1 (default: 1)

Button Component

Creates styled buttons with multiple variants:

import {Button} from "@/components/Button"

// Primary button (default)
<Button href="https://app.netbird.io/install" arrow="right">
  Get started
</Button>

// Secondary button
<Button href="/path" variant="secondary">
  Learn more
</Button>

// Outline button
<Button href="/path" variant="outline">
  Explore
</Button>

// Text button
<Button href="/path" variant="text" arrow="right">
  Read more
</Button>

// With left arrow
<Button href="/path" arrow="left">
  Back
</Button>

Props:

  • variant (string, optional): Button style - 'primary', 'secondary', 'filled', 'outline', or 'text' (default: 'primary')
  • href (string, optional): Link URL (creates a link if provided, otherwise renders as button)
  • arrow (string, optional): Arrow icon - 'left' or 'right'
  • children (required): Button text content

Other Common Components

Row and Col

Create two-column layouts:

import {Row, Col} from "@/components/mdx"

<Row>
  <Col>
    Left column content
  </Col>
  <Col sticky>
    Right column content (sticky on scroll)
  </Col>
</Row>

Properties and Property

Define API properties or configuration options:

import {Properties, Property} from "@/components/mdx"

<Properties>
  <Property name="apiKey" type="string" required>
    Your API key for authentication.
  </Property>
  <Property name="timeout" type="number" min={0} max={300}>
    Request timeout in seconds (default: 30).
  </Property>
</Properties>

Badge

Displays small status badges:

import {Badge} from "@/components/mdx"

<Badge>New</Badge>
<Badge variant="secondary">Beta</Badge>

Code Blocks

Code syntax highlighting (automatically available):

\`\`\`bash
npm install
npm run dev
\`\`\`

// Or use code groups for multiple languages
<CodeGroup>
  ```bash title="Installation"
  npm install
yarn install
```

Thank you

NetBird thrives on community participation, and we appreciate your contributions to our website and our documentation!

S
Description
No description provided
Readme BSD-3-Clause
314 MiB
Languages
MDX 91.6%
JavaScript 7.4%
TypeScript 0.5%
Shell 0.2%
CSS 0.1%