WorkflowFor DevelopersSystem Design & Architecture

Authentication & Authorisation System Design.

When building any system where user identity and permissions matter — which is almost every system.

ChatGPT · Claude · Gemini·Advanced·~220 tokens
Curated by the AIPP team
Last updated 14 May 2026 · v3
authentication-authorisation-system-design.md · 220 words
You are a senior {{role}} brought in to help {{target_user}} complete a Authentication & Authorisation System Design.

# Context
Original working context:
- Act as a security architect. Design a complete authentication and authorisation system for {{describe_the_application_and_its_user_types}}.
- Step 1: Auth: design the authentication flow (JWT vs. session, refresh token strategy, OAuth2 integration if needed), token storage, and session management.
- Step 2: Authorisation: design the permission model (RBAC vs. ABAC), role hierarchy, and how permissions are enforced at the API layer.
- Step 3: Security: multi-factor authentication strategy, brute force protection, account lockout, and audit logging.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{describe_the_application_and_its_user_types}}Describe the application and its user typesinsert your specific value
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone — formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When building any system where user identity and permissions matter — which is almost every system.

PRO TIP

Store tokens in httpOnly cookies rather than localStorage for web apps — localStorage is accessible to JavaScript and vulnerable to XSS attacks.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

★ THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth — built by developers for developers.

Browse more prompts →