UI/UX & Website Prompts
Permissions and Role Management UX Designer
Design understandable permission and role interfaces that expose consequences, prevent accidental lockout, and support safe review and recovery.
FreeClaudeChatGPT
Best for
Enterprise product teams making complex roles and permissions safer and more understandable for nontechnical administrators.
Suitable LLM groups
FrontierReasoning
Prompt
You are an enterprise UX specialist who designs clear role, permission, access-request, and administration experiences.
Inputs:
1. Product, organizations, users, and administrative roles: {{system_context}}
2. Resources, actions, scopes, and permission model: {{permission_model}}
3. Common administration tasks and approval flows: {{admin_tasks}}
4. Security risks, audit needs, and support history: {{risk_evidence}}
5. Platform, accessibility, compliance, and technical constraints: {{constraints}}
Do the following:
1. Translate technical permissions into user-recognizable resources, actions, scope, duration, and consequences, identifying conflicts or combinations that users cannot reasonably understand.
2. Design role creation, assignment, comparison, access request, approval, expiration, revocation, and periodic review flows with least-privilege defaults.
3. Specify warnings, previews, confirmations, dependency handling, inherited-access explanations, mixed states, bulk changes, and safeguards against self-lockout or removal of the last administrator.
4. Define empty, loading, stale, unauthorized, partial-failure, concurrent-change, and recovery states plus audit-history and notification behavior.
5. Produce an information model, task flows, screen specifications, permission-language glossary, risk-based confirmation rules, and usability plus security test scenarios. Do not simplify away material security consequences.How to use
- List actual resources, actions, scopes, and inheritance rules.
- Include previous access mistakes and support questions.
- Define high-risk and irreversible changes.
- Test terminology with real administrators.
Example input
Product: Multi-tenant research repository. Roles: organization owner, workspace admin, researcher, external reviewer, and custom roles. Resources: projects, files, participant data, exports, billing, and integrations. Tasks: invite reviewers for 30 days, restrict participant data, transfer ownership, and audit exports. Evidence: two customers accidentally gave reviewers workspace-wide access; support receives questions about inherited project permissions. Constraints: GDPR, SSO groups, WCAG 2.2 AA, and one owner must always remain.
Example output
The design replaces broad technical labels with action-and-scope summaries such as “View files in Project Atlas until 30 August.” External reviewer defaults exclude participant data, exports, billing, and integrations. Assignment includes an effective-access preview showing inherited SSO and workspace permissions. High-risk changes require consequence-based confirmation, ownership transfer verifies another owner first, and partial bulk failures identify exactly which assignments changed. Tests cover inherited access, expiration, self-lockout, and concurrent edits.
Customization tips
- — Show effective access, not only assigned roles.
- — Use time-limited access where appropriate.
- — Explain inherited permissions at the point of confusion.
- — Protect the last administrator or owner explicitly.
Tags
#permissions-ux#role-management#enterprise-ux#access-control#admin-interface
FAQ
What is this prompt for?
It designs role and permission management so administrators understand effective access and change consequences.
How should I customize it?
Provide the permission model, resources, scopes, roles, administrative tasks, inheritance, security risks, audits, and technical constraints.
Are there any limitations?
UX cannot compensate for a flawed authorization model, and security engineers must verify that implementation matches displayed effective access.
How is it different from a basic prompt?
It translates technical permissions into consequences and specifies inheritance, previews, expiry, bulk failure, lockout prevention, audit, and recovery states.
Related Prompts
All UI/UX & Website prompts →Free
Dashboard Information Hierarchy Designer
Structure a dashboard around decisions, exceptions, comparisons, and drill-down paths instead of filling a grid with disconnected metrics.
ClaudeChatGPT
#dashboard-design#information-hierarchy#data-ux
Free
Accessibility Quick Audit
Reviews a described website or app interface against core accessibility principles, flagging likely issues for users with visual, motor, or cognitive differences.
ClaudeChatGPT
#accessibility#ui-ux#wcag
Free
First-Run Onboarding Flow Architect
Design a progressive onboarding flow that gets users to their first meaningful outcome without unnecessary setup or premature education.
ClaudeChatGPT
#user-onboarding#product-activation#first-run-experience
Related Skills
UI & Web BuildingFree
Permission and Role Management UX Architect
Design role and permission experiences with mental models, access levels, invitations, explanations, previews, conflicts, recovery, and audit visibility.
ClaudeChatGPT
#permission UX#role management#admin experience
UI & Web BuildingFree
Data Table and Bulk Action UX Architect
Design complex data tables and bulk actions with columns, selection, filtering, editing, permissions, feedback, performance, accessibility, and recovery.
ClaudeChatGPT
#data table UX#bulk actions#admin interface
Safety, Privacy & ComplianceFree
Multi Tenant Authorization Architect
Design multi-tenant authorization with roles, permissions, object ownership, tenant isolation, admin boundaries, and tests.
ClaudeChatGPTCursor
#multi-tenant authorization#RBAC#ABAC
Related articles coming soon — visit the Learn hub.