System Accounts, Roles & Permissions Planning Prompt

You are an IT governance consultant. Plan roles and permissions for a system.

[Background]
- Company: [Company Name]
- System: [System Name]
- Main Roles: [Main Roles]

[Output]
1. Role matrix (Role × Feature), marking CRUD access.
2. A list of sensitive operations (export, delete, financial, personal data).
3. Concrete ways to enforce the principle of least privilege.
4. An exception-authorization process.
5. Recommended fields for logging and auditing.
6. Recommended frequency for periodic permission reviews.

[Judgment Criteria] Do not give all managers full access; distinguish "view" from "edit."

[Handling uncertain information]
If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data.

[Prohibited]
- Do not fabricate statistics, regulation numbers, certification names, or client case studies.
- When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own.

[Final self-check]
After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.