Your account
HOL-D094Story implementation: In progress

Invite and remove organization managers

organizations · Proposed launch phase 2

Start from Home

Review as Organization owner

User story

As a organization owner, I want to invite and remove managers so my team can maintain our page using their own accounts.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Only the current organization owner may invite or remove managers; managers cannot change team access or ownership.
  • Bind each invitation to the intended recipient, organization, limited manager permission and expiring/single-use acceptance; show pending, accepted, expired and revoked states.
  • An invitee signs in or registers using their own account and verifies email before accepting. Invitation links alone, different recipients or forwarded links cannot grant management.
  • Accepted managers can edit/publish basic organization details under D084. Show the active organization; organization membership creates no HOL staff or Commercial Partner authority.
  • Remove manager access promptly for the affected organization while retaining their personal account, reader/professional access and other organization assignments. Review own removal without self-restoring.
  • Keep organization team controls in the named organization context with existing owner-only invitation/removal rules; shared personal settings never grant organization management or financial rights.

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 owner’s named organization Home select Team & ownership. The feature starts at Invite registered account email and Invite manager.

Feature checks start here

Invite and remove organization managers

Connected in dev; full acceptance remains In progress. Owner invitation persists across reload and the intended account can accept. Managers publish basic facts while owner-only team/transfer controls stay hidden; removal/revoke/expired/replayed browser cases remain open.

  1. 03As owner enter Invite registered account email and select Invite manager. Use a dedicated verified recipient account that already exists.
  2. 04In the recipient’s own session use account/workspace menu → Invitations & requests and accept the intended organization invitation. Open its named workspace and Basic page.
  3. 05Compare Team & ownership as an accepted manager: invite, remove and transfer controls are owner-only. Expired/wrong-recipient/reused/removal cases require prepared invitations; do not change real reviewer access just to populate the walkthrough.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Persist org membership and recipient-bound invitation with inviter, intended recipient, manager scope, token digest/expiry, accepted/revoked state and audit. Check inviter still owns that org when acceptance occurs.
  • 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.
  • Use organization-scoped owner/manager records rather than the internal staff-assignment table. Require verified email for organization creation, claims, management and invite acceptance.
  • Bind invite acceptance to the intended verified account; expire/revoke/single-use invitations and check current inviter ownership at acceptance.

How to verify in dev

  1. Test wrong-recipient, forwarded, expired, revoked and reused invitation acceptance; remove a manager and verify immediate org-specific denial with unchanged private account and other org access.
  2. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  3. 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