Skip to content

Commit 31a372e

Browse files
committed
docs: update sign-in-restriction
1 parent 2ea1a4f commit 31a372e

File tree

1 file changed

+14
-22
lines changed

1 file changed

+14
-22
lines changed

content/docs/administration/sign-in-restriction.md

Lines changed: 14 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -2,48 +2,40 @@
22
title: Sign-in Restriction
33
---
44

5-
This document explains some sign-in restrictions.
5+
<HintBlock type="info">
6+
7+
Only **Workspace Admin** can update the settings.
8+
9+
</HintBlock>
610

711
## Sign-in Frequency
812

913
<PricingPlanBlock feature_name='SIGNIN_FREQUENCY' />
1014

1115
**Sign-in Frequency** specifies the period that users are required to sign in again.
1216

13-
Only **Workspace Admin** can update the **Sign-in Frequency** settings.
14-
15-
In Bytebase Workspace, Go to **Settings** -> **General** and scroll down to **Account** section, where you can
16-
17-
- Choose between `Hour(s)` and `Day(s)`.
18-
- Click `+`,`-` or input a number to set the **Sign-in Frequency**.
17+
In Bytebase Workspace, Go to **Settings** -> **General** and scroll down to **Account** section.
1918

2019
![sign-in-frequency](/content/docs/administration/sign-in-restriction/sign-in-frequency.webp)
2120

22-
<HintBlock type="info">
23-
24-
You need to restart Bytebase and re-login to make the change take effect.
25-
26-
</HintBlock>
21+
You need to restart Bytebase to make the change take effect.
2722

2823
## Disallow Sign-in with Email & Password
2924

3025
<PricingPlanBlock feature_name='SSO' />
3126

32-
As `Workspace Admin`, having had [SSO](https://www.bytebase.com/docs/administration/sso/overview) (for example [OAuth 2.0 in GitHub](https://www.bytebase.com/docs/administration/sso/oauth2/#github)) configured, you can [enforce SSO sign-in](https://www.bytebase.com/docs/administration/sso/overview/#enforce-sso-sign-in) for all users in Workspace.
27+
Once [SSO](/docs/administration/sso/overview) is configured, you can [enforce SSO sign-in](/docs/administration/sso/overview/#enforce-sso-sign-in) for all users.
3328

3429
## Sign-in from Email Domains
3530

36-
Go to **Settings** -> **General**, scroll down to **Security** section. Fill in `Workspace Domain` tab with the email domain for your Workspace members. Click **Update** to save changes.
31+
Go to **Settings** -> **General**, scroll down to **Security** section. Fill in `Workspace Domain` tab with the email domain for your Workspace members. Then tick the `Members restriction` box.
3732

3833
![set-domain](/content/docs/administration/sign-in-restriction/set-domain.webp)
3934

40-
You can restrict members' email addresses by ticking the `Members restriction` box. Afterwards, when you
41-
- Sign in (Note that the new restriction only works for the accounts registered after the `Workspace Domain` was updated)
42-
![sign-in-domain-restriction](/content/docs/administration/sign-in-restriction/sign-in-domain-restriction.webp)
43-
44-
or
35+
Domain restriction applies to:
4536

46-
- **Add User** in **IAM & Admin** -> **Users & Groups**
47-
![add-user-domain-restriction](/content/docs/administration/sign-in-restriction/add-user-domain-restriction.webp)
37+
- Sign-in page. (Note that the new restriction only applies to the accounts registered after the `Workspace Domain` was updated)
38+
![sign-in-domain-restriction](/content/docs/administration/sign-in-restriction/sign-in-domain-restriction.webp)
4839

49-
Users' email must be of the domain you set in both scenarios.
40+
- **Add User** in **IAM & Admin** -> **Users & Groups**. Users' email must be of the domain you set in both scenarios.
41+
![add-user-domain-restriction](/content/docs/administration/sign-in-restriction/add-user-domain-restriction.webp)

0 commit comments

Comments
 (0)