access-requests@ hasn't been migrated from RT yet. Let's use this task to follow the progress.
So migrating the existing content of this queue to Phabricator isn't a priority for us, but given that we'll likely receive most new requests in Phabricator anyway, we'll need to make this work in some shape or form. Let's create this project and figure out a (manual) workflow for now, and optimize it later.
Migrating the existing RT content can happen when we also do the procurement queue; as long as we still can refer to the existing (resolved) tickets in RT itself we should be fine for now.