> ## Documentation Index > Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt > Use this file to discover all available pages before exploring further. # Choose which CRM accounts enter Quivly > Use reviewed account conditions and won-opportunity criteria to focus imports on the customers you want. [Back to What's new](https://docs.quivly.ai/changelog.md) [](https://docs.quivly.ai/updates/2026-10.md) v1.22.0 # Choose which CRM accounts enter Quivly Use reviewed account conditions and won-opportunity criteria to focus imports on the customers you want. Work with your Quivly onboarding team to choose whether to import all CRM accounts or only accounts that meet reviewed conditions, such as customer status or a related won opportunity. These eligibility rules are separate from the field mappings that decide which values populate each record. Monaco and Octolane initial setup requires an explicit account scope and saved object mappings. Ordinary field-mapping saves preserve the scope already configured. Tightening an import condition does not delete customers already in Quivly. Read about [CRM import scope](https://docs.quivly.ai/field-mappings/introduction.md#which-crm-accounts-are-imported). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.