From f630770ab8c09a6230f8e59e6f8051f4bf0e818d Mon Sep 17 00:00:00 2001 From: David Date: Wed, 11 Dec 2024 14:26:44 -0800 Subject: [PATCH] additions to trusted domains config details (#630) --- src/docs/reference/teams.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/docs/reference/teams.md b/src/docs/reference/teams.md index 153fc72b1..6c1697fbf 100644 --- a/src/docs/reference/teams.md +++ b/src/docs/reference/teams.md @@ -27,6 +27,14 @@ There are three roles for Team members: *Note*: Changes that trigger a deployment will skip the approval requirement when the author has a Deployer role (or higher) and their Github account is connected. ## Trusted Domains +Trusted domains may be configured on the team settings page. Note that team members added via trusted domain will be billed at the normal rate. + +Trusted domains are configurable via the team settings You can automate the onboarding of new team members with trusted domains. Railway users that sign up with one of the trusted domains associated with your team will automatically be granted access to the team with the specified role (see above).