This article explains how contacts are added to private groups, how imports affect group membership and visibility, and what to check so the right users can see and manage imported contacts.
Overview
Contacts can be added to private groups in multiple ways, including direct subscription and imports. The way you import or synchronize contacts determines:
- Which private or child groups the contacts belong to
- Whether additional groups are created during import
- Who can view and manage the imported contacts
Ways contacts are added to a private group
Contacts belong only to the specific private group to which they were added.
- Direct subscription (opt-in): Contacts can be directly subscribed to a private group when they opt in.
- Import into a specific group: Contacts can also be added by importing them into a specific private (or child) group.
If you import contacts into a child or private group, those contacts will appear in that group and contribute to any parent group's aggregate count if the parent aggregates nested groups. They are not automatically listed as direct members of other groups unless you add them there separately.
Where imported contacts appear
Imported contacts appear only in the group you target during the import. They do not become direct members of other groups by default.
To verify where imported contacts are stored:
- Open the group you imported into.
- Download or view that group's contacts.
Importing contacts without creating groups
If you want to add contacts but not create any groups as part of the import, use an API-based contact upload workflow instead of a manual file upload.
- API uploads can add contacts without creating groups.
- If you need a clean import with no pre-existing groups or contacts, remove the existing contact and group data first, then perform the API upload.
With this approach, only the contacts are added, and no new groups are created by the import itself.
How import methods affect group membership and visibility
Imported contacts can be handled differently depending on how they are uploaded or synchronized.
- If contacts are imported on a schedule (for example, nightly), confirm whether the import process assigns contacts to groups or leaves them unassigned.
- Check whether the import sets ownership or visibility settings that might restrict who can view and manage those contacts.
- Contact integration or synchronization via API and file upload via SFTP each have different behaviors and configuration options for ownership, group assignment, and visibility.
Review your import configuration so that imported contacts are visible to the roles that need to manage them. If they are not, adjust role permissions as described in the roles documentation. For a comparison of import methods and configuration details, see the contact integration and import options documentation.