ENGDOCS-2812 (#23661)

<!--Delete sections as needed -->

## Description

Moves some remaining enterprise FAQs 

## Related issues or tickets

<!-- Related issues, pull requests, or Jira tickets -->

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review

Author: aevesdocker

content/manuals/docker-hub/usage/pulls.md

@@ -51,7 +51,7 @@ Attribution is based on the following:
   determined based on domain affiliation and organization membership.
 - Verified domain ownership: When pulling an image from an account linked to a
   verified domain, the attribution is set to be the owner of that
-  [domain](/manuals/security/faqs/single-sign-on/domain-faqs.md).
+  [domain](/manuals/enterprise/security/single-sign-on/faqs/domain-faqs.md).
 - Single organization membership:
    - If the owner of the verified domain is a company and the user is part of
      only one organization within that

content/manuals/security/faqs/single-sign-on/_index.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/_index.md

@@ -1,5 +1,5 @@
 ---
 build:
   render: never
-title: Single sign-on
----
+title: FAQs
+---

content/manuals/security/faqs/single-sign-on/domain-faqs.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/domain-faqs.md

@@ -7,6 +7,7 @@ tags: [FAQ]
 aliases:
 - /single-sign-on/domain-faqs/
 - /faq/security/single-sign-on/domain-faqs/
+- /security/faqs/single-sign-on/domain-faqs/
 ---
 
 ## Can I add sub-domains?

content/manuals/security/faqs/single-sign-on/enforcement-faqs.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/enforcement-faqs.md

@@ -7,6 +7,7 @@ tags: [FAQ]
 aliases:
 - /single-sign-on/enforcement-faqs/
 - /faq/security/single-sign-on/enforcement-faqs/
+- /security/faqs/single-sign-on/enforcement-faqs/
 ---
 
 ## Does Docker SSO support authenticating through the command line?

content/manuals/security/faqs/single-sign-on/faqs.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/general.md

@@ -11,6 +11,7 @@ aliases:
 - /single-sign-on/saml-faqs/
 - /faq/security/single-sign-on/saml-faqs/
 - /security/faqs/single-sign-on/saml-faqs/
+- /security/faqs/single-sign-on/faqs/
 ---
 
 ## What SSO flows does Docker support?

content/manuals/security/faqs/single-sign-on/idp-faqs.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/idp-faqs.md

@@ -7,6 +7,7 @@ tags: [FAQ]
 aliases:
 - /single-sign-on/idp-faqs/
 - /faq/security/single-sign-on/idp-faqs/
+- /security/faqs/single-sign-on/idp-faqs/
 ---
 
 ## Can I use multiple identity providers with Docker SSO?

content/manuals/security/faqs/single-sign-on/users-faqs.md renamed to content/manuals/enterprise/security/single-sign-on/FAQs/users-faqs.md

@@ -7,6 +7,7 @@ tags: [FAQ]
 aliases:
 - /single-sign-on/users-faqs/
 - /faq/security/single-sign-on/users-faqs/
+- /security/faqs/single-sign-on/users-faqs/
 ---
 
 ## Do I need to manually add users to my organization?
@@ -36,7 +37,7 @@ For detailed instructions, see [Configure single sign-on](/manuals/enterprise/se
 
 ## Is Docker SSO fully synced with the IdP?
 
-Docker SSO provides Just-in-Time (JIT) provisioning by default. Users are provisioned when they authenticate with SSO. If users leave the organization, administrators must manually [remove the user](../../../admin/organization/members.md#remove-a-member-or-invitee) from the organization.
+Docker SSO provides Just-in-Time (JIT) provisioning by default. Users are provisioned when they authenticate with SSO. If users leave the organization, administrators must manually [remove the user](/manuals/admin/organization/members.md#remove-a-member-or-invitee) from the organization.
 
 [SCIM](/manuals/enterprise/security/provisioning/scim.md) provides full synchronization with users and groups. When using SCIM, the recommended configuration is to turn off JIT so all auto-provisioning is handled by SCIM.
 

content/manuals/enterprise/security/single-sign-on/_index.md

@@ -67,5 +67,5 @@ Using a PAT ensures continued CLI access. For more information, see the
 ## Next steps
 
 - Start [configuring SSO](configure.md).
-- Read the [FAQs](/manuals/security/faqs/single-sign-on/faqs.md).
+- Read the [FAQs](/manuals/enterprise/security/single-sign-on/faqs/general.md).
 - [Troubleshoot](/manuals/enterprise/troubleshoot/troubleshoot-sso.md) SSO issues.