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

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

Example for: A multi-tenant analytics dashboard feature with roles: Admin, Manager, Analyst, Contributor, and Viewer.

Access Control Matrix
RoleReadCreateEditDeleteAudit
AdminYesYesYesYesYes
ManagerYesYesYesNoYes
AnalystYesYesYesNoNo
ContributorYesYesNoNoNo
ViewerYesNoNoNoNo
Security Logic
  1. Delete permissions are restricted to the Admin role to prevent accidental data loss or malicious destruction of historical records.
  2. Audit logs are accessible to Managers and Admins to ensure oversight on account activity and compliance reporting.
  3. The Contributor role is limited to creation and reading to protect existing configurations from unauthorized modification.
  4. The Viewer role is read-only to ensure the integrity of the dashboard data for non-technical stakeholders.

This is not legal or security advice; consult a qualified security professional for production implementation.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.

Product Management

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.