Every ImportMappingProfile carries a tenantId that controls visibility. Profiles you create in your organization are only available to users within the same tenant — another organization's lab mappings never appear in your import workflow. This ensures that your custom columnMapping and labName configurations remain private and cannot be accidentally applied to another tenant's import batches. The tenantId is set automatically when the profile is created and enforced on every lookup during the file import process.
piper
Import Mapping Profile Tenant
The `tenantId` on an ImportMappingProfile scopes the profile to a single organization so that mapping configurations are never shared across tenants.