For the pilot and in the short term, engineers with access to prod DB Proofing Agent table can manually create approved Proofing Agents but we should consider how this might be managed by a program administrator or like role in the future.
Thinking beyond the 1st pilot, we may need to think about creating an admin page to add authorized Proofing Agents. I'd image it would only be accessible to software admins (which is a concept we haven't implemented in the codebase). And the page would be a form with entries for:
email
given_name
family_name
And maybe they need to verify that the person is trained and authorized to proof. These could be checkboxes that disable the submit button. Once they are checked, the submit button could be enabled and the new PA can be added the DB.
For the pilot and in the short term, engineers with access to prod DB
Proofing Agent
table can manually create approved Proofing Agents but we should consider how this might be managed by a program administrator or like role in the future.From Slack thread: