Your account
HOL-D084Story implementation: In progress

Prepare and publish public organization profiles

people · Proposed launch phase 2

Start from Home

Review as Organization owner

User story

As a organization owner, I want to publish our organization’s basic page updates so visitors can find accurate business information.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Owner and accepted managers may edit and publish basic organization name, categories, description, logo/image, website, business location, service areas and offerings without HOL editorial approval.
  • Require verified email and current authority for this specific organization; ordinary members, former managers and staff without assigned organization authority cannot use the self-service edit route.
  • Provide draft, preview, publish, correction and unavailable/retry states; show the named organization and preserve canonical identity and public links.
  • Affiliations require both sides’ agreement under D098. Editing a page cannot self-grant a verified badge, sponsorship, Commercial Partner status or access to private member data.
  • Keep partner applications, sponsorship placements and canonical editorial publication under their separate approval workflows. Basic business-page publishing has no HOL review gate.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.

Navigation from sign-in

  1. 01Open the fictional Organization owner account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02From the named organization Home select Basic page. The feature starts at Basic organization facts; there is no separate Edit page button.

Feature checks start here

Basic page · Basic organization facts

Connected in dev; full acceptance remains In progress. Verified owner and accepted manager publish actual versioned organization facts to the public detail page. No HOL editorial approval is required for these basic facts; stale/concurrent UI checks remain open.

  1. 03On Basic page edit Name, Categories, Description, Business location, Website, Logo image address, Broad service areas and Offerings as appropriate.
  2. 04Use Save private draft, then Publish basic page. Follow View public page and compare the published organization; there is no HOL approval queue for basic facts.
  3. 05Repeat using the accepted manager account. Team & ownership explains the owner-only controls. Test unrelated/unverified/former access and stale edits with dedicated review fixtures; do not transfer or remove a stakeholder’s access as routine setup.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Use one trusted account ID; keep email verification, professional labels, reader entitlement, organization-scoped access and internal HOL staff assignments independent.
  • Validate actor, organization/person IDs, current access and expected revision at the trusted boundary. Remembered workspace, URL, fixture choice and client flags never grant permissions.
  • Persist only the records needed for this outcome, including owner-scoped drafts and decision/assignment/consent audit where applicable. Keep private evidence and contacts out of public projections.
  • Enforce the selected requirements above in database/API policies, with idempotent transitions, concurrent-update handling and denied cross-account writes.
  • Use isolated local synthetic data only; no hosted migration, public service connection, real credentials/recipients, live payment or deployment.

How to verify in dev

  1. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  2. Exercise success, interrupted/repeated requests, expiry/revocation and stale/concurrent updates; verify stable identity, correct public visibility and preserved unrelated account data.

Before this can work

  • Begin in a named organization workspace as its current owner. The local Organization owner choice uses Maya Hart → Teton Meadow Guides; current assignments may change during reviews. Choose the organization in the account/workspace menu. Personal account security remains separate.
  • Use a fictional organization owner account and begin at its Home with its actual permitted context.
  • Use actual local provider sessions and persisted state; record connected UI and direct permission checks separately.

Connected stories