A nutrition and health coaching portal is where clients log their meals and weekly check-ins, and each coach reads the entries of their own clients and no one else's.
Pattern: TrackingDescribe it to Pory
“Our nutrition coaching practice wants clients to log meals and a weekly check-in, and each coach to see only the clients assigned to them.”
My log entries
| Leftover dal and rice | Oct 15, 2026 | Meal | Good | — | |
| Overnight oats with berries | Oct 14, 2026 | Meal | Good | — | |
| Sheet-pan salmon with greens | Oct 13, 2026 | Meal | Good | — | |
| Week 3 check-in | Oct 11, 2026 | Weekly check-in | OK | 7 | |
| Week 2 check-in | Oct 4, 2026 | Weekly check-in | OK | 6.5 |
Showing 1–5 of 5
In plain English
Pory gives every client and coach a sign-in of their own. Each client sees only their own log entries. It covers meal logs & check-ins. Log entries, clients, calls, forms, resources, invoices and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Food diaries arrive as screenshots, texted photos of a sandwich, and a check-in email every other Sunday if the week went well. Clients log each meal and a short weekly check-in here, with the date, what they ate and how their energy held up. The coach reads a week of entries in one list instead of scrolling a camera roll.
In a shared spreadsheet every coach can scroll through every client's food diary, which is awkward for clients and a risk for the practice. Here each client is linked to one coach, and that coach's lists show only the people they work with: their program, goal and stage, their log entries, forms and calls. Adding a coach doesn't mean handing them the whole client list.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own log entries.
Sees the log entries assigned to them.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited clients.
