Google Workspace sections.

docs/directory-sync/faq.md

@@ -7,8 +7,6 @@ sidebar_label: FAQ
 
 Frequently asked questions about the issues and limitations of the directory sync providers.
 
-### Okta
-
 #### Why don't I see a DELETE event for a user that was removed in Okta?
 
 Instead of executing a DELETE operation, Okta sends a request to the SCIM application to set the `active` attribute to `false`. Consequently, you will observe a `user.updated` event with the `active` attribute changed to `false` for users removed from the Okta application.
@@ -17,14 +15,10 @@ Instead of executing a DELETE operation, Okta sends a request to the SCIM applic
 
 Okta does not dispatch a specific deprovisioning event for users that are suspended. This omission of a deactivation event is a known issue with Okta.
 
-### OneLogin
-
 #### Why don't I see any event when a group is removed in OneLogin?
 
 It is a known issue with OneLogin SCIM. OneLogin does not dispatch a specific deprovisioning event for groups that are deleted, so you won't see any event such as `group.deleted` or `group.user_removed` when a group is removed. It is recommended to remove the users from the group before deleting the group itself from the SCIM application.
 
-### Google Workspace
-
 #### Does Google Workspace sync in real time?
 
 No, Google Workspace sync is not real-time. Jackson syncs the Google Workspace directory on a schedule (e.g. every 2 hours). In a self-hosted deployment, you can configure a cron job to sync the directory on a schedule of your choice.