Which level of access must a running user have to an object referred to in a lookup component in a screen flow?

In a screen flow, when utilizing a lookup component to reference an object, the running user must have at least read access to that object. Read access allows the user to view the records of the object in question, which is essential for presenting the options within the lookup component.

If the running user does not have read access, they wouldn't be able to see or select any records from the lookup. On the other hand, create and edit access go beyond what is necessary just to view records. Create access would specifically allow the user to add new records, while edit access permits modifying existing records. Neither of these permissions is required to simply reference existing records in a lookup component. Modify All access is an even broader permission that enables a user to edit and delete records regardless of sharing rules, but it is not a prerequisite to using the lookup component effectively.

Therefore, having read access ensures that the user can interact appropriately with the lookup component to select from existing records in that object, making it a fundamental necessity in this context.