You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* sign up copy nits
* first pass at new onboarding page
* wip join onboard logic
* refactor auth provider fetch logic
* add member approval and invite link flag logic
* update join request flow and remove jit logic
* onboard guard
* nits, onboard role check, invite link enabled check
* fix bg color issue in onboarding page
* refactor onboard UI
* ui nits and more onboarding resource cards
* revamp auth docs
* change member approval default behavior and updated docs
* merge prisma migrations
* add id to resource card
* feedback
* feedback
* feedback and fixed build
* settings drop down UI nit
* ui nits
* handle join when max capacity case
* add news data for member toggle
* refactor for public access case
* add iap bridge to onboard logic
* fetch member approval req and invite link enabled flag on server
* ui nits
* fix invite link enable toggle snapping issue
* ui nits
* styling and ui nits, pass in invite id from server
* add mcp resource in onboard step
* get invite link in server
* fix build issue
* refactor docs on config
* minor doc nit
- Makes base retry indexing configuration configurable and move from a default of `5s` to `60s`. [#377](https://github.com/sourcebot-dev/sourcebot/pull/377)
13
14
- Fixed issue where files would sometimes never load in the code browser. [#365](https://github.com/sourcebot-dev/sourcebot/pull/365)
If member approval is enabled, new members will be asked to submit a join request after signing up. They will not have access to the Sourcebot deployment
21
+
until this request is approved by the owner.
22
+
23
+
The owner can see and manage all pending join requests by navigating to **Settings -> Members**.
24
+
25
+
## Invite link
26
+
27
+
If member approval is required, an owner of the deployment can enable an invite link. When enabled, users
28
+
can use this invite link to register and be automatically added to the organization without approval:
29
+
30
+

<Warning>If you're deploying Sourcebot behind a domain, you must set the [AUTH_URL](/docs/configuration/environment-variables) environment variable.</Warning>
6
6
7
-
Sourcebot has built-in authentication that gates access to your organization. OAuth, email codes, and email / password are supported.
7
+
Sourcebot's built-in authentication system gates your deployment, and allows administrators to manage users and their permissions.
Have a question about Sourcebot's auth system? We might have the answers here.
21
+
</Card>
22
+
</CardGroup>
8
23
9
-
The first account that's registered on a Sourcebot deployment is made the owner. All other users who register must be [approved](/docs/configuration/auth/overview#approving-new-members) by the owner.
10
-
11
-

12
-
13
-
14
-
# Approving New Members
15
-
16
-
All account registrations after the first account must be approved by the owner. The owner can see all join requests by going into **Settings -> Members**.
17
-
18
-
If you have an [enterprise license](/docs/license-key), you can enable [AUTH_EE_ENABLE_JIT_PROVISIONING](/docs/configuration/auth/overview#enterprise-authentication-providers) to
19
-
have Sourcebot accounts automatically created and approved on registration.
20
-
21
-
You can setup emails to be sent when new join requests are created/approved by configurating [transactional emails](/docs/configuration/transactional-emails)
22
-
# Authentication Providers
23
-
24
-
To enable an authentication provider in Sourcebot, configure the required environment variables for the provider. Under the hood, Sourcebot uses Auth.js which supports [many providers](https://authjs.dev/getting-started/authentication/oauth). Submit a [feature request on GitHub](https://github.com/sourcebot-dev/sourcebot/discussions/categories/ideas) if you want us to add support for a specific provider.
25
-
26
-
## Core Authentication Providers
27
-
28
-
### Email / Password
29
-
---
30
-
Email / password authentication is enabled by default. It can be **disabled** by setting `AUTH_CREDENTIALS_LOGIN_ENABLED` to `false`.
31
-
32
-
### Email codes
33
-
---
34
-
Email codes are 6 digit codes sent to a provided email. Email codes are enabled when transactional emails are configured using the following environment variables:
35
-
36
-
-`AUTH_EMAIL_CODE_LOGIN_ENABLED`
37
-
-`SMTP_CONNECTION_URL`
38
-
-`EMAIL_FROM_ADDRESS`
39
-
40
-
41
-
See [transactional emails](/docs/configuration/transactional-emails) for more details.
42
-
43
-
## Enterprise Authentication Providers
44
-
45
-
The following authentication providers require an [enterprise license](/docs/license-key) to be enabled.
46
-
47
-
By default, a new user registering using these providers must have their join request accepted by the owner of the organization to join. To allow a user to join automatically when
48
-
they register for the first time, set the `AUTH_EE_ENABLE_JIT_PROVISIONING` environment variable to `true`.
-`AUTH_EE_GITLAB_BASE_URL` - Base URL for GitLab instance (defaults to https://gitlab.com)
73
-
74
-
### Google
75
-
---
76
-
77
-
[Auth.js Google Provider Docs](https://authjs.dev/getting-started/providers/google)
78
-
79
-
**Required environment variables:**
80
-
-`AUTH_EE_GOOGLE_CLIENT_ID`
81
-
-`AUTH_EE_GOOGLE_CLIENT_SECRET`
82
-
83
-
### GCP IAP
84
-
---
85
-
86
-
<Note>If you're running Sourcebot in an environment that blocks egress, make sure you allow the [IAP IP ranges](https://www.gstatic.com/ipranges/goog.json)</Note>
87
-
88
-
Custom provider built to enable automatic Sourcebot account registration/login when using GCP IAP.
89
-
90
-
**Required environment variables**
91
-
-`AUTH_EE_GCP_IAP_ENABLED`
92
-
-`AUTH_EE_GCP_IAP_AUDIENCE`
93
-
- This can be found by selecting the ⋮ icon next to the IAP-enabled backend service and pressing `Get JWT audience code`
Sourcebot supports a wide range of different authentication providers through it's integration with [Auth.js](https://authjs.dev/). This page
6
+
highlights how to configure the various supported providers.
7
+
8
+
If theres an authentication provider you'd like us to support, please [reach out](https://www.sourcebot.dev/contact).
9
+
10
+
# Core Authentication Providers
11
+
12
+
### Email / Password
13
+
---
14
+
Email / password authentication is enabled by default. It can be **disabled** by setting `AUTH_CREDENTIALS_LOGIN_ENABLED` to `false`.
15
+
16
+
### Email codes
17
+
---
18
+
Email codes are 6 digit codes sent to a provided email. Email codes are enabled when transactional emails are configured using the following environment variables:
19
+
20
+
-`AUTH_EMAIL_CODE_LOGIN_ENABLED`
21
+
-`SMTP_CONNECTION_URL`
22
+
-`EMAIL_FROM_ADDRESS`
23
+
24
+
25
+
See [transactional emails](/docs/configuration/transactional-emails) for more details.
26
+
27
+
# Enterprise Authentication Providers
28
+
29
+
The following authentication providers require an [enterprise license](/docs/license-key) to be enabled.
-`AUTH_EE_GITLAB_BASE_URL` - Base URL for GitLab instance (defaults to https://gitlab.com)
54
+
55
+
### Google
56
+
---
57
+
58
+
[Auth.js Google Provider Docs](https://authjs.dev/getting-started/providers/google)
59
+
60
+
**Required environment variables:**
61
+
-`AUTH_EE_GOOGLE_CLIENT_ID`
62
+
-`AUTH_EE_GOOGLE_CLIENT_SECRET`
63
+
64
+
### GCP IAP
65
+
---
66
+
67
+
<Note>If you're running Sourcebot in an environment that blocks egress, make sure you allow the [IAP IP ranges](https://www.gstatic.com/ipranges/goog.json)</Note>
68
+
69
+
Custom provider built to enable automatic Sourcebot account registration/login when using GCP IAP.
70
+
71
+
**Required environment variables**
72
+
-`AUTH_EE_GCP_IAP_ENABLED`
73
+
-`AUTH_EE_GCP_IAP_AUDIENCE`
74
+
- This can be found by selecting the ⋮ icon next to the IAP-enabled backend service and pressing `Get JWT audience code`
Sourcebot can sync code from generic git repositories stored in a local directory. This can be helpful in scenarios where you already have a large number of repos already checked out. Local repositories are treated as **read-only**, meaing Sourcebot will **not**`git fetch` new revisions.
8
+
Sourcebot can sync code from generic git repositories stored in a local directory. This can be helpful in scenarios where you already have a large number of repos already checked out. Local repositories are treated as **read-only**, meaning Sourcebot will **not**`git fetch` new revisions.
0 commit comments