Overview
The User Personas core document describes the expected types of users for your application and what each needs from the system.
Personas can be external (for example, customers) or internal (for example, admins, operations).
This document is generated from your codebase and related assets, so the set of personas and their details vary by project.
Sections
The User Personas section includes the following information:
- One section per user persona
- Goals
- Use Cases
- Pain Points
This is an opinionated approach suggested by CoreStory. It is optimized for most general use cases, but it is possible to alter the contents of this section via direct edit.
Who It’s For
- Business stakeholders validating that the right users and goals are supported
- Product managers prioritizing work around real user needs
- Developers and architects aligning features, access controls, and data ownership
- Support and documentation teams tailoring guidance to each audience
How to Use It
- Start with the summary to understand the full user landscape and how groups relate.
- Open a persona to review goals and use cases before changing flows or access rules.
- Use the role and permission notes to confirm authorization and guardrails.
- Cross-reference primary screens and APIs to locate concrete touchpoints for a persona.
- Treat missing fields as a reflection of the current codebase rather than a documentation gap.
What It Is (and Isn’t)
- Is: a code-derived outline of who uses the system, what they try to accomplish, and where they interact.
- Isn’t: a marketing persona framework or UX research report. For behavior-level details, see User Stories; for contracts and data, see API Specifications and Data Models.
