Academic Data Governance Access Request Workflow Script

Role: Lead Academic Data Governance and Research Security Architect.

Context

• Research Consortium: {{academic_consortium}}
• Protected Data Asset: {{data_asset_name}}
• Security & Compliance Standard: {{governance_standard}}
• Target Researcher Profile: {{requester_category}}
• Required Clearance Level: {{security_clearance_tier}}
• Compliance Audit Cycle: {{audit_frequency}}

Task

Design a multi-step automated email workflow script for handling incoming research access requests to {{data_asset_name}}, ensuring rigorous compliance with {{governance_standard}} while facilitating legitimate scholarly inquiries.

Method

1. Evaluate access prerequisites for {{requester_category}} against {{security_clearance_tier}} governance parameters.
2. Draft Email 1 (Automated Intake Confirmation): Sets researcher expectations, outlines verification criteria, and lists required documentation.
3. Draft Email 2 (Conditional Clarification / Deficient Submission): Targeted script prompting applicants to resolve credential, ethics board, or compute environment gaps.
4. Draft Email 3 (Approval & Onboarding): Formal authorization containing credential activation instructions, data boundaries, and {{audit_frequency}} obligations.
5. Draft Email 4 (Formal Policy Rejection): Defensible, courteous rejection script citing precise policy criteria without exposing internal security controls.
6. Embed programmatic tokens (e.g., {{ticket_id}}, {{expiry_date}}) and decision-tree logic within each template.
7. Structure a comprehensive security disclaimer reminding users of sanctions regarding data re-identification or unapproved exports.

Constraints

• MUST align all authorization parameters strictly with {{governance_standard}}.
• MUST NOT provide subjective or ambiguous justifications for application rejections.
• MUST explicitly detail the continuous monitoring parameters and {{audit_frequency}} in all approval scripts.
• Scripts must maintain a professional, academic, yet uncompromisingly security-conscious tone.

Output format

• Section 1: Data Access Workflow Lifecycle Diagram (Text-based status state machine).
• Section 2: Complete Email Script Sequence (4 distinct operational scripts: Intake, Info Request, Approval, Denial).
• Section 3: Periodic Audit Warning Script (Re-attestation notification dispatched ahead of {{audit_frequency}}).

Self-review

• Verify that each script clearly states the security boundaries governing {{data_asset_name}}.
• Confirm that the denial script provides unambiguous recourse instructions without violating data governance secrets.
• Ensure the approval script incorporates strict re-attestation timelines.