tnl.dev :: docs

teams.

Create teams, invite members, and manage shared public URLs.

choose a team

Every identity has a personal team. Create an organization team to share domains and public URLs with other identities. Team selection is per tnl server; a project can pin its team in configuration.

tnl team list
tnl team current
tnl team create studio
tnl team use studio

team create creates an organization team. Its name is the unique, stable selector for --team and project configuration; on a self-hosted server it also appears in managed-domain URLs. Use one lowercase DNS label, 1–63 characters, made of letters, digits, and internal hyphens: studio or design-team, not Studio or Design Team. Personal team names are assigned once from a readable identity-name candidate, adding a suffix if needed; later identity display-name changes do not rename them. team use saves a team for commands without a project team. Without a saved selection, your personal team is used. A project team setting takes precedence over the saved selection on that project's server.

By default, the creator's member slug is derived once from the identity's stored display name, for example Chase Adams becomes chase-adams. Hosted accounts retain their sign-in identity; self-hosted OIDC uses its stored identity name. Matching email addresses do not merge identities. If a usable slug cannot be derived, pass --member-slug. Choose it explicitly before creation when you want a particular namespace:

tnl team create studio --member-slug chase

Member slugs are immutable: chase becomes part of custom-domain URLs such as web.chase.studio.example.com and, in simple mode, managed URLs such as web.chase.studio.routes.example.com. The hosted server opts into separate generated labels on its managed domain. Run tnl team current --team studio or tnl team members --team studio to check a derived slug before publishing; later changes to your GitHub or OIDC profile name do not change it.

For a one-command override, pass --team to tnl domain, tnl url, or a team-scoped command. The flag does not change the saved selection:

tnl domain list --team studio --server=https://control.example.com
tnl team invite list --team studio

When you explicitly select a server other than the project's configured server, tnl uses that server's saved or personal team unless you also pass --team. tnl team list shows the saved and project selections separately.

invite a member

An admin or owner can invite a member. An owner can also grant the initial admin or owner role. Choose a team-unique --member-slug before inviting: it reserves an immutable label used in custom-domain namespaces and in simple-mode managed namespaces.

tnl team invite create --member-slug sam --role member --email sam@example.com --expires-in 168h
tnl team invite list

On the hosted tnl server, --email restricts acceptance to that verified address and queues an email with a link to tnl.dev/invite. The recipient signs in with an available shared provider and confirms joining. The create command still writes the invitation ID and secret once, so you can share it privately. Without --email, share the secret yourself. A self-hosted server needs its invitation mailer configured to send mail; --email still restricts acceptance independently. team invite list does not return secrets. --role defaults to member, and --expires-in defaults to 168h.

The invited identity can also accept the secret in the CLI and select the joined team:

tnl team join INVITATION_SECRET

If an invitation is no longer needed, revoke it by ID:

tnl team invite revoke INVITATION_ID

manage membership

tnl team members
tnl team members --team studio
tnl team member set-role MEMBERSHIP_ID --role admin
tnl team member remove MEMBERSHIP_ID

Roles are member, admin, and owner. Members can publish in their own namespace. Admins can manage member invitations, add custom domains, choose the default domain, and publish shared public URLs. Owners can also change roles, invite admins or owners, and release custom domains. Admins may remove members; owners may remove other roles. The last owner cannot be removed or demoted. Membership removal revokes that membership's publishing access. See Domains for namespace labels and DNS setup.

company access and departures

Use tnl auth login --team studio for company-authenticated control access. The same device approval flow selects the team and binds the actual provider sign-in; team use alone does not establish company authentication.

An owner can configure one company identity connection for an organization team. Directory eligibility and source authentication are separate requirements. Owner-approved requests or managed admission grant only member access; role changes remain explicit tnl operations. A hosted account can explicitly link another provider at /a/sign-in, but linking is not sign-in with that source. No email-domain match claims a team.

Owners can explicitly allow a particular contractor invitation or membership to use personal sign-in. Provider updates do not clear that policy. Manual suspension is reversible and separate from role or exception. Directory loss suspends member-owned access/runs while current eligibility is absent; manual removal is not automatically undone by sync. Team-owned unattended publishers continue when their creator leaves. A newly eligible employee may still need a fresh company sign-in, and a replacement source may require owner approval to rebind membership.

share a public url

On a custom domain, an admin or owner can publish a complete hostname outside an individual's namespace. For example, after studio.example.com is ready for studio:

tnl publish web --public-url https://preview.studio.example.com
tnl url list

A shared public URL belongs to the team. A member can publish under their own member slug instead, for example web.sam.studio.example.com. Organization team-shared URLs require a custom domain; on a self-hosted managed domain only the built-in administrator's personal team can publish direct URLs. tnl url delete PUBLIC_URL_ID removes a saved public URL when it is no longer wanted. A member can delete their own public URL; admins and owners can delete team public URLs.