- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Scoring
- Question Types
- Question Authoring
- Browsing Questions
- Content Blocks
- Media Library
- Metadata Rules & Schema
- Roles & Access
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
Question Bank Supervisor: Role & Responsibilities
Question Bank Supervisor grants full Question Bank access plus the submission review queue — it's the role for someone whose main job is curating the bank and acting as its quality gate, without needing broader organization access.
Question Bank Supervisor is the role for someone whose job is the question bank itself: authoring, organizing, and — when the submission workflow is in use — reviewing what outside contributors send in. It grants full Question Bank access plus the review queue, without handing over anything else in the organization.
What Access It Grants
- Full Question Bank access — browsing, creating, editing, organizing questions, exactly like an Editor or Manager would have.
- Submission Reviews — the Pending and Resolved queues, with the Approve, Revise, and Reject actions.
Admin, Manager, and Editor also see Submission Reviews — review access comes bundled with their broader organization permissions. Question Bank Supervisor exists for the case where someone should get exactly that combination (bank + reviews) without any of the rest of those roles' organization-wide access.
Duties as the Quality Gate
- Review promptly. Contributors are blocked from resubmitting or knowing where they stand until a submission is acted on — a stale Pending queue stalls every author behind it.
- Give feedback that's actually actionable. Both Revise and Reject require a message; write it so the contributor knows exactly what to fix or exactly why it was declined — not just "needs work."
- Get the directory right on Approve. Approving is also the moment to set the question's real folder, tags, language, and labels — whatever the contributor's submission carried over is what ships if you don't override it.
- Be the actual gate, not a rubber stamp. Approval publishes the submission's content exactly as written — there is no supervisor edit step, so a question with a fixable content issue should go back as Revise, not be approved with the intent to fix it later.
See Reviewing & Approving Submissions for the moment-to-moment mechanics of the review queue.