A guided account area for resources and coaching clients.

Member access is designed to organize workbook resources, teaching libraries, private coaching prep, files, invoices, and follow-up in the right place. Visitors can start with public resources now and use account access when it applies.

Access check

Use the email connected to your member or coaching-client access. If you do not have access yet, start with the workbook or Clarity Call.

Mike Jaja guiding a faith-centered coaching conversation with study materials.

Account access should support the coaching relationship, not distract from it.

The account page keeps member access tied to the client experience before showing resources, access lanes, and support expectations.

Move from public resources into protected client work only when it helps.

The account page follows a simple access model: public discovery first, member resources second, private coaching records last.

Each privacy lane has its own use case.

These lanes prevent public content, free starter resources, member materials, coaching records, and team work from sharing one vague account bucket.

Public

Articles, videos, book pages, campaigns, link hub, shop gateway, and creative gateway can be visible without account state.

Free

Workbook delivery, selected teachings, and starter resources can be tied to consent and email without paid membership.

Member

Paid or gated resources should require authenticated member profile and subscription checks before access.

Coaching

Client prep, deliverables, comments, files, invoices, and project history require coaching-specific memberships.

Private

Internal notes, team controls, unpublished content, proof reviews, and support triage should stay team-only.

Admin

Publishing, user management, support review, and safety checks require role-gated admin access.

Access issues should be helpful and private.

Member access should handle password help, duplicate signup, expired links, private files, and team-only areas without exposing account status.

Wrong password

After repeated failures, show a neutral message, slow down attempts, and avoid confirming whether the email exists.

Password help

Password help should feel useful without revealing whether an account or private membership exists.

Duplicate signup

An existing email should not reveal private membership, subscription, or coaching-client status.

Expired link

Verification and recovery links should fail gracefully after expiry or repeated use.

Unauthorized file

A member who is not assigned to a coaching project should not download its files or see private file paths.

Team-only page

Publishing, user management, internal notes, and support review should stay closed to regular members.

A dashboard shape for members, coaching clients, and team support.

The tabs below show how an account can organize resources without mixing public materials, member content, and private coaching details.

Workbook Access

Workbook delivery, consent-aware follow-up, and saved progress when member access applies.

Coaching Prep

Private prep prompts, readiness notes, and upcoming-session next steps.

Member Videos

Curated teaching playlists, replays, transcript pages, and topic progress.

Deliverables

Session worksheets, reflection plans, PDF downloads, and client-ready files.

Invoices and Terms

External invoice links, signed terms, and payment status references.

Support

Restricted support paths for coaching and member questions without mixing crisis disclosures into general inboxes.

Open member access in layers, not all at once.

This keeps the site useful while avoiding premature collection of private credentials, files, notes, invoices, or support records.

Sign-in

Account access should use clear invitations, trusted redirects, neutral errors, and helpful recovery language.

Files

Private coaching files should stay behind member access before upload or download fields are shown.

Payments

Invoices and subscriptions can reference external providers without exposing private coaching context.

Activity

Member events should record consent, access decisions, and support status without storing unnecessary sensitive text.

Forms should protect the person behind the request.

Every account form should validate the right fields before it creates member, coaching, support, file, or billing records.

Workbook signup
Validate email, consent source, policy version, duplicate handling, and delivery status server-side.
Account profile
Validate account identity, allowed fields, role changes, subscription state, and profile visibility before updating records.
Coaching update
Validate project membership, published/internal state, comment visibility, and sensitive-content guidance.
File upload
Validate file type, size, path, bucket, project assignment, and signed-access rules before storing.
Support request
Validate request type, crisis or sensitive flags, spam protection, and response lifecycle without leaking private details.
Invoice reference
Validate provider, status, amount display rules, and access before showing billing rows.

Protect the member area before inviting users in.

No signup, uploads, invoices, or private coaching notes should open until the member experience is ready to support them.

Require proof, not a good-looking dashboard.

The dashboard can demonstrate structure. Member access still needs clear privacy fit, access rules, protected files, trusted links, and support responsibilities.

  1. 01

    Policies

    Privacy, terms, coaching scope, crisis language, and cookie/data notes match the actual portal behavior.

  2. 02

    Access rules

    Member resources, coaching records, private files, and team-only areas have reviewed access rules.

  3. 03

    Private keys

    Private provider credentials, payment tokens, and service keys stay out of browser code and public files.

  4. 04

    Spam and rate limits

    Signup, reset, contact, workbook, support, and anonymous paths have limits and bot protection.

  5. 05

    Trusted links

    Account emails, redirects, and API calls use approved production domains and known services.

  6. 06

    Review result

    Access, privacy, and support findings are resolved or documented before invitations go out.

The account surface is shaped for private resources and client support.

Member resources, coaching project records, deliverables, private files, invoices, comments, and activity should stay organized by access level.

ProfilesTiersSubscriptionsResourcesResource AccessEventsClientsPortal MembershipsProjectsDeliverablesFilesUpdatesInvoicesCommentsActivity Log

Use public resources while member access stays guided.

Visitors should start with the workbook, videos, book, or Clarity Call. Member accounts are for resources and coaching support that require protected access.