> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-hk/sso/enable-and-verify.md).
# 第五步：啟用並驗證登入
## 5.1 啟用企業登入
在 **安全 → 企業登入 → 企業登入（SSO）** 區塊最上方的開關控制啟用狀態，切換後即時生效。
* 尚未儲存企業身份源時開關不可點，會提示：**先填寫並儲存企業身份源，才能啟用企業登入**。
* 首次儲存企業身份源後會自動啟用，開關顯示「已啟用」。
## 5.2 驗證登入
建議用**無痕視窗**測試，避免既有登入狀態干擾：
{% stepper %}
{% step %}
## 開啟登入頁
{% endstep %}
{% step %}
## 選擇企業登入並輸入組織代碼
{% endstep %}
{% step %}
## 完成企業身份源登入
頁面跳轉到企業身份源（Okta），完成登入。
{% endstep %}
{% step %}
## 確認成功進入團隊
登入成功後回到系統，確認能正常進入團隊。
{% endstep %}
{% endstepper %}
驗證後回到 **通訊錄 → 成員**，開啟剛才登入的成員，「企業帳號」一列應顯示 **已綁定**。
## 5.3 驗證統一登出（若已開啟）
{% stepper %}
{% step %}
## 以企業帳號登入系統
{% endstep %}
{% step %}
## 執行登出
{% endstep %}
{% step %}
## 確認登出流程
確認會跳轉到企業身份源並完成登出，且最後能回到系統的登入頁。
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
若停在企業身份源的登入頁回不來，通常是「登出回跳地址」沒有登記到對方的應用設定裡。
{% endhint %}
## 5.4 停用企業登入
關閉開關會先出現確認提示：
{% hint style="warning" %}
**關閉企業登入？** 關閉後，成員暫時不能用企業帳號登入。成員的 SSO 帳號和綁定都會保留，重新開啟後可以繼續使用。
{% endhint %}
也就是說，停用是可逆的，不會清掉已建立的綁定關係。
## 推廣給成員前的檢查清單
* [ ] 組織代碼已確定，且不打算再更動
* [ ] 企業身份源設定已儲存，開關顯示「已啟用」
* [ ] Okta 應用已指派給所有需要使用的使用者／群組
* [ ] 測試帳號可正常登入，成員詳情顯示「已綁定」
* [ ] 有例外電郵／手機的成員已單獨設定企業帳號
* [ ] （若使用統一登出）登出回跳地址已登記，登出流程測試通過
* [ ] 已把組織代碼與登入方式通知成員
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.coreway.com/coreway-hr/zh-hk/sso/enable-and-verify.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
