GETTING STARTED

Roles: owner, exec, assistant, reader

3 min read · Updated Jul 2026 · Applies to all plans

CoverQueue has four roles. They decide what each person can see and do, from running the whole log to reading a single assigned script. Set a person's role when you invite them from Settings → Members; owners can change roles later.

The four roles

  • Owner: full control, including members, roles, templates, and billing. There's always at least one.
  • Exec: reads coverage, records decisions, assigns readers, creates share links, and manages templates. Can't manage members or billing.
  • Assistant: runs the log day to day: logs and imports submissions, assigns readers, creates share links, writes coverage if assigned.
  • Reader: a scoped freelancer who sees only the submissions assigned to them, writes and signs their own coverage, and never sees the rest of your slate.

What each role can do

A few capabilities from the permissions matrix:

Capability              Owner  Exec  Assistant  Reader
View all submissions     yes   yes     yes      assigned only
Assign readers           yes   yes     yes        no
Write coverage           yes   yes   if assigned  assigned only
Create share links       yes   yes     yes        no
Manage templates         yes   yes      no        no
Manage members/roles     yes    no      no        no
Tip

Execs and assistants overlap heavily on the day-to-day log. The clearest line is upward: only owners manage members, roles, and billing.

Deactivating someone

Owners can deactivate a member from Settings → Members. Deactivation doesn't reassign their open work automatically, so you'll see a warning about any submissions still assigned to them; reassign those first.

Heads up

Readers are the confidentiality boundary of the product. Before inviting a freelancer, read Reader accounts and what they can see so you know exactly what they can and can't reach.

Common questions

Can I change someone's role later? Yes. Owners change roles from the Members table.

How are roles enforced? In the database, via row-level security, not just in the interface. A reader literally cannot query submissions they aren't assigned to.

Was this helpful?