Reader accounts and what they can see
Freelance readers are hired per script. A reader needs to see the scripts assigned to them, write coverage, sign, and be done, and must never see the rest of your slate. CoverQueue enforces exactly that.
What a reader sees
A reader signs in to a reduced shell: My Assignments, a list of the submissions assigned to them, and the scoped detail view for each. From there they can read the script in the in-app viewer, download a watermarked copy, and write and sign their coverage.
They do not see the submission log, other writers, search, share links, or anyone else's coverage. There is no way to navigate to a submission they weren't assigned.
Assigning a reader emails them a magic link that drops them straight into that submission: low-friction onboarding with no password to set up.
Enforced at the database level
Reader isolation isn't just a hidden menu item. It's enforced by row-level security in the database and is covered by a dedicated automated test suite. A reader's account cannot query submissions outside their assignments even in principle.
After signing
Once a reader signs their coverage, the assignment moves to a Done section. Depending on your organization's setting, the reader keeps read access to their own signed coverage, but not necessarily the script itself.
Reader seats are a paid feature: Free has none, Solo includes two, and Team is unlimited. See Plans, trials, and what happens after for the limits.
Common questions
Can a reader see who else is on the team? No. Readers don't see the members roster or any submission they weren't assigned.
Can a reader be assigned more scripts later? Yes. Each assignment adds a submission to their My Assignments list; nothing else becomes visible.
Do readers need a password? No. Like everyone else, readers sign in with a magic link.