Permissions and Roles Matrix Design
Define who can do what.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a roles and permissions matrix. Product and user types: [PRODUCT_AND_USERS]. Actions and data in the system: [ACTIONS_AND_DATA]. Compliance needs: [COMPLIANCE_NEEDS]. Output format: 1. A matrix. Rows are actions (view, create, edit, delete, approve, export, invite, manage billing, change settings); columns are roles (owner, admin, manager, member, viewer, external guest); each cell is allowed, own items only, or denied. 2. Special rules: separation of duties for approvals, limits on exporting personal data, and what happens when a user's role changes or they leave. 3. The five rules that govern exceptions, such as temporary access with an expiry date, and how a permission request is approved and logged. 4. The least-privilege principle applied: which role gets the fewest rights by default. 5. An audit-log requirement: who did what and when. 6. Edge cases: the last admin is removed, ownership transfer, shared items. 7. Ten test scenarios in Given/When/Then form. Flag regulatory questions [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.