Define Granular Role-Based Access Control for Multi-Tenant Features
Generate a clear, professional permission matrix mapping five standard user roles to granular read, create, edit, delete, and audit actions for your feature.
Prompt
You are a Senior Product Manager. Your task is to define the Role-Based Access Control (RBAC) permissions for a new software feature. Please ask me these three questions first and wait for my response: 1. What is the name and core function of the feature? 2. What are the five primary user roles involved in your system? 3. Are there any specific regulatory or security compliance requirements I should consider? Once I answer, provide the RBAC matrix. Follow these rules: 1. Create a table with rows for roles and columns for permissions (Read, Create, Edit, Delete, Audit). 2. Use 'Yes', 'No', or 'Owner Only' for each cell. 3. Include a brief section explaining the logic behind the most restrictive permission settings. Output format: A table followed by a 'Security Logic' section. This is not legal or security advice; consult a qualified security professional for production implementation.Example output
Tips and common edits
Why this works
- Requires the model to gather context before generating the matrix.
- Enforces a clear, standardized table format for easy stakeholder review.
- Includes a security logic section to explain the reasoning behind restrictions.
Use this prompt when designing the security architecture for a new feature in a B2B SaaS application. It works best in ChatGPT, Claude, or Gemini. Have your role definitions and feature scope ready before starting.
Common edits
- Add a custom column for 'Export' if your feature handles sensitive data.
- Adjust the roles to match specific organizational titles like 'Billing Admin' or 'Guest' if needed.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Classify onboarding drop-offs into cognitive and value friction
Audit user onboarding funnels by separating confusion from missing value motivation. Use it to prioritize growth experiments and UX redesigns.
Define beta cohorts and launch exit metrics
Build a structured cohort plan and clear release criteria for your upcoming beta launch. Use this to prevent feature creep and ambiguous testing timelines.
Draft a customer advisory board charter
Create a clear operational charter for a customer advisory board. Use it to align senior executives, define member terms, and prevent sessions from becoming feature wishlists.
Rewrite empty state copy to accelerate user activation
Turn passive placeholder screens into clear, action-oriented entry points that guide users to their first completed task. Use it during product design and copy polish.
Schedule phased customer communications for feature sunsetting
Create a structured, multi-channel communication timeline to retire a software feature without alarming customers or breaking workflows.
Analyze customer feedback using Jobs to Be Done
Extract functional, emotional, and social customer drivers from raw user feedback. Use this to separate true user motivations from reactionary feature requests.
- Design an in-app micro-survey for churned users
- Reframe a feature request into a core user problem
- Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
- Draft Multi-Tier SaaS Product Packaging and Feature Matrix
- Stress Test Your Product Requirements Document for Edge Cases
- Audit Feature Adoption Tracking Across User Workflows