Guide 07 · Developer docs

Building a member area on Core dna: who a member is in the data, the sign-in flows and their templates, single sign-on and passkeys, the my-account routing convention, members-only content, sessions and the page cache, and the security checks to run before launch.

Unit 04 of 07 4 pages

The my-account area and its routing convention

Updated 23/10/2026 01:44

How the members-only area under /my-account is routed: the screens the platform ships, the catch-all that turns a template into a page, and what to use when a page needs more. For theme developers building or restyling a member area.

The member area is one dispatcher. Named routes serve the built-in screens, and a last route maps any other path straight onto a template under templates/my-account/, so a members-only page needs no route and no admin configuration. The convention is simple, and the rules around it (what a missing file does, which names are taken, what the template receives) are what a team needs written down.

Start with How the member area is routed, which states the mapping rule and its edges. The built-in member screens is the reference for restyling: each screen's template, its variables, and which ones the framework leaves to you. Adding a custom member page is the three-step procedure, and When the catch-all is not enough covers forms, ids in the path, other access rules and data for scripts. Who may sign in, and how, is in the units before this one; deciding what a signed-in member may see is in the unit after it.

In this unit

Read in order

01 How the member area is routed Every URL under /my-account goes through one dispatcher: named routes for the built-in screens, then a catch-all that turns a template in templates/my-account/ into a members-only page. The mapping rule, what wins when names collide, and what the template receives. 02 The built-in member screens The screens the platform serves under /my-account: each one's route name, the template it renders and the variables it receives, which ones the framework ships a template for, and the account menu they share. 03 Adding a custom member page A members-only page needs a template and a deploy, nothing else: no page record, no route and no admin setting. The procedure, the file it takes, how to put it in the account menu, and what it does and does not protect. 04 When the catch-all is not enough The catch-all serves a GET with the signed-in user and nothing else. What to use instead when a member page has to take a form, carry an id in its path, follow other access rules or feed a script.

Objects ReferenceGenerated from the platform, so it is always current

API ReferenceEvery REST endpoint, in cURL, PHP, Python and JavaScript

The my-account area and its routing convention

In this unit