Test the organization flow - manual QA checklist

[0xdevcollins]

Manual QA issue for the organization flow in Boundless: creating organizations, managing profile/settings, members and invitations, navigation, archive/delete, and public org profile. Use this to run through the flows and record any bugs or UX issues.

Scope

• App area: /organizations and all org sub-routes; /org/[slug] (public profile); /accept-invitation/[invitationId].
• Auth: Flows assume the tester is signed in unless noted (e.g. public profile, accept-invitation).
• Backend: Depends on Better Auth organization APIs and backend org/hackathon APIs (e.g. NEXT_PUBLIC_API_URL). Invitations and member list depend on backend/Better Auth behavior.

---

1. Entry points & navigation

Entry	URL / Action	What to check
Org list	Nav → “Organizations” or /organizations	Redirects to org dashboard when logged in; list loads or empty state shows.
New org	“Add Organization” / “Create Organization” → /organizations/new	Redirects to create flow; auth guard sends unauthenticated users to sign-in.
Org dashboard	Click an org card from /organizations	Card click sets active org and navigates to /organizations/[id]; sidebar and breadcrumbs reflect current org.
Layout	Any /organizations/... (except /organizations and /organizations/new)	Header shows breadcrumbs (Organizations > Org name > …); sidebar shows Hackathons, Settings, “Host Hackathon”; mobile shows hamburger sidebar.
Public profile	Direct or shared link /org/[slug]	Loads org by slug; metadata/OG correct; “Organization not found” when slug invalid or backend error.

Things to point out

• Org ID in URL: Dashboard/settings/hackathons use ID (/organizations/[id]/...). Layout derives orgId from path and expects ID format (e.g. 24-char hex). If the backend ever returns or links using slug in these paths, links can break.
• Breadcrumbs: Second crumb uses activeOrg.name; if org is slow to load, name can be blank or show a skeleton.
• Header org selector: OrganizationSelector is commented out in OrganizationHeader.tsx; quick actions (e.g. “Host Hackathon”, “New Organization”) still depend on activeOrg / path.

---

2. Create organization

Step	Action	What to check
2.1	Go to /organizations/new	Profile tab only (no Links/Members/Transfer); form empty.
2.2	Fill Name	Slug auto-derives (e.g. from slugify(name)); can override manually.
2.3	Slug field	Debounced slug check (e.g. authClient.organization.checkSlug); UI shows available/taken/invalid (e.g. min length).
2.4	Tagline & About	Both required on submit; clear validation messages.
2.5	Logo	Optional; upload (or URL if supported); preview updates.
2.6	Submit	Create org (Better Auth organization.create); success toast; redirect to /organizations/[newOrgId]/settings after short delay.
2.7	Duplicate slug	Try creating another org with same slug when “taken”; backend/checkSlug should block or show error.

Things to point out

• Required fields: Name, tagline, about are enforced; empty optional fields (e.g. links) should not block create.
• Slug source: Slug is sent to backend; public profile uses slug (/org/[slug]). Ensure create/update keep slug unique and URL-safe.
• Post-create: Redirect goes to settings (not dashboard); user can then open “Hackathons” from sidebar.

---

3. Organization settings (existing org)

Step	Action	What to check
3.1	Open /organizations/[id]/settings	Tabs: Profile, Links, Members, Transfer Ownership.
3.2	Profile	Name, slug, logo, tagline, about, links load from activeOrg (or initialData). Edits save via updateOrganization; success/error toasts.
3.3	Links	Website, X, GitHub, others; save persists and survives refresh.
3.4	Members	List of members; roles; “Invite by email” and pending invitations (if backend supports).
3.5	Transfer Ownership	Only for owner; flow and confirmation; backend must enforce.

Things to point out

• Active org sync: Settings page calls setActiveOrg(organizationId) on mount so sidebar/header context is correct when navigating from list or direct URL.
• Slug edit: Changing slug on profile affects /org/[slug]; ensure slug check runs on edit (exclude current org) and duplicate slug is rejected.

---

4. Members & invitations

Step	Action	What to check
4.1	Settings → Members	Members list loads (Better Auth / backend); roles and avatars/names if returned.
4.2	Invite by email	Add one or more emails; “Invite” calls authClient.organization.inviteMember per email; success/error toasts; pending invitations appear.
4.3	Pending list	Shows email, role, expiry; “Cancel” calls cancel-invitation API; list updates after cancel.
4.4	Accept invitation (invitee)	Open link /accept-invitation/[invitationId] (invitee logged in or after sign-in). Accept runs authClient.organization.acceptInvitation; success → redirect to /organizations/[organizationId]; error → message and “Go to Home”.
4.5	Accept invitation (invalid/expired)	Use wrong or expired invitationId; expect error state and clear message.

Things to point out

• Invitation link: Must use invitationId (e.g. from email); link format and env (e.g. NEXT_PUBLIC_APP_URL) must match so invitee lands on the app.
• Permissions: Only owners can cancel invitations; others see an error (e.g. “Only organization owners can cancel invitations”).
• Member list after invite: Depends on backend; if members are refetched after invite, list should update; same for cancel.

---

5. Organization list & actions

Step	Action	What to check
5.1	/organizations	Cards show name, logo, created date, hackathon count, grant count; archived orgs have “Archived” and different style.
5.2	Search	Filter by name; empty state when no match; “Clear search” resets.
5.3	Sort	Newest / Oldest / Name A–Z / Name Z–A; order persists while on page.
5.4	Edit (card menu)	“Edit Organization” → /organizations/[id]/settings.
5.5	Archive	Confirm dialog; archive API; toast; if archived org was active, redirect to /organizations; card shows “Archived” and “Unarchive”.
5.6	Unarchive	Confirm; unarchive API; toast; card returns to normal.
5.7	Delete	Delete dialog with checkbox “I understand…”; delete only enabled when checked; delete API; toast; redirect to /organizations if deleted org was active.

Things to point out

• Delete: Irreversible; copy states that hackathons, grants, submissions, settings are deleted. Confirm checkbox prevents misclicks.
• Archive vs delete: Archive hides from “active” list but keeps data; delete is permanent. Confirm backend behavior matches UI.
• Card click: Clicking card (not menu) sets active org and goes to /organizations/[id]; loading state (e.g. isThisOrgLoading) should prevent double navigation.

---

6. Sidebar & quick actions

Step	Action	What to check
6.1	From org context	Sidebar: Hackathons, Grants (disabled), Settings; Quick actions: “Host Hackathon”, “Create Grants” (disabled).
6.2	“Host Hackathon”	Goes to /organizations/[id]/hackathons/new.
6.3	“Settings”	Goes to /organizations/[id]/settings (or “New Organization” when derivedOrgId is missing).
6.4	Mobile	Hamburger opens sheet with same nav; no layout shift or wrong org.

Things to point out

• Grants: “Grants” and “Create Grants” are disabled (coming soon); no 404 or broken links.
• Org context: Sidebar uses pathname to derive derivedOrgId; on /organizations/[id]/hackathons/... the correct org is used for links.

---

7. Public organization profile

Step	Action	What to check
7.1	Open /org/[slug] (valid slug)	Fetches getOrganizationProfile(slug); shows name, description, etc.; metadata/OG for sharing.
7.2	Invalid slug	“Organization not found” or error state.
7.3	OG image	/api/og?slug=... used for social preview; image and title/description correct.

Things to point out

• Slug vs ID: Public URL is slug; dashboard/settings use ID. Ensure backend profile by slug is stable and that orgs with incomplete profile (e.g. missing tagline) don’t break the page.

---

8. Edge cases & cross-cutting

Area	What to check
Auth	Sign out from org page → redirect or clear state; sign in again → org list and active org make sense.
Loading	Org list loading spinner; active org loading (e.g. breadcrumb skeleton); no flash of wrong org name.
Errors	Network/server errors show toast or inline message; no uncaught errors or white screen.
Deep links	Direct URL to /organizations/[id]/settings or /organizations/[id]/hackathons loads with correct org and sidebar.
Search (header)	⌘K / search opens OrganizationHeaderSearch; if backend supports GET /organizations/search?q=..., results and navigation work (see docs/BACKEND_ORGANIZATION_SEARCH.md).

---

9. Acceptance checklist (summary)

• Can open /organizations and see list or empty state; “Create Organization” and “Add Organization” work.
• Can create org with name, slug, tagline, about (and optional logo); slug check works; redirect to settings after create.
• Can edit profile and links; save persists; slug uniqueness enforced on edit.
• Members tab loads; can invite by email; pending invitations show and can be cancelled (as owner); accept-invitation link works and redirects to org.
• List search and sort work; archive/unarchive and delete (with confirmation) work; redirect when active org is archived/deleted.
• Sidebar and breadcrumbs show correct org; “Host Hackathon” goes to new hackathon; mobile sidebar works.
• Public /org/[slug] loads for valid slug; not found for invalid slug; OG/metadata correct.
• No console errors or unhandled rejections during the above flows; loading and error states are clear.

---

10. Files to keep in mind

Area	Files
Routes	app/(landing)/organizations/page.tsx, .../new/page.tsx, .../[id]/page.tsx, .../[id]/settings/page.tsx, app/(landing)/accept-invitation/[invitationId]/page.tsx, app/(landing)/org/[slug]/page.tsx
Layout	app/(landing)/organizations/layout.tsx (org ID from path, sidebar visibility)
List & cards	components/organization/OrganizationContent.tsx, components/organization/cards/OrganzationCards.tsx
Settings	components/organization/OrganizationSettings.tsx, tabs/ProfileTab.tsx, tabs/LinksTab.tsx, tabs/MembersTab.tsx, tabs/TransferOwnershipTab.tsx
Header & sidebar	components/organization/OrganizationHeader.tsx, components/organization/OrganizationSidebar.tsx
Delete	components/organization/DeleteOrganizationDialog.tsx
Provider	lib/providers/OrganizationProvider.tsx (create, update, delete, archive, setActiveOrg, fetch orgs)

Use this issue for manual test runs and paste any failures or unclear behavior (with steps and env) as comments so the team can fix or refine the flow.

[bitstarkbridge]

I’d like to work on this issue because it directly impacts reliability and developer experience. Problems around deployment, repository configuration, and contract/network mismatches can block contributors entirely, so resolving them has immediate value for both the maintainers and the broader user base. I’m particularly motivated by issues that require careful debugging and clear documentation, since solving them not only fixes the immediate bug but also improves the overall workflow and prevents future regressions.

[edehvictor]

Hello 0xdevcollins,
I'd love to work on this. I fully understand how to resolve the issue. Kindly assign.
ETA:3hrs

[Austinaminu2]

Hi,

I’d like to work on this issue.

I have experience with Next.js applications, QA testing, and debugging frontend/backend integrations. I will run through the full organizations flow including creation, settings, members/invitations, navigation, archive/delete actions, and the public org profile. I’ll document any bugs, UX issues, or edge cases encountered with clear reproduction steps.

ETA: within 3–4 hours.

Please assign this issue to me.

[soma-enyi]

Gm Gm Maintainer!!!!
I woud like to work o this issue!!!!

[auracule007]

Hi maintainers, I'm Promise Adedokun. I'm a full-stack developer with experience in manual QA and testing complex user flows. I'd like to work on this manual QA checklist. I can run through the complete organization flow covering creation, settings, members/invitations, list actions, sidebar navigation, public profiles, and edge cases documenting any bugs, UX issues, or inconsistencies I find. My ETA is 3-4 hours.

[Ekene001]

Can i handle this?

I’ve looked over the scope and can have a full QA report ready in under 24 hours. I have plenty of experience running manual end-to-end tests and breaking down complex flows like organization management, so I’m comfortable hunting for edge cases in the invitation and member settings.

I’ll start by running through the creation flow and the public profile views to make sure the routing is seamless. I’ll pay close attention to the Better Auth integration, specifically testing how invitations are accepted and how member permissions update in real-time. I’ll also test the "danger zone" actions like archiving or deleting an organization to ensure the state updates correctly across the app. Once I’m done, I’ll provide a clear log of any bugs or UX hitches I find so they can be fix.

Please assign this to me.

[Agbeleshe]

Hello, please can I tackle this issue? I’m a frontend developer with over 3 years of experience working with React, Next.js, and TypeScript, and I’m very comfortable performing structured manual QA across complex UI flows, including authentication, organization management systems, and API-driven dashboards. I have experience testing applications that rely on context providers, role-based access, and backend integrations such as Better Auth APIs, and I’m skilled at documenting bugs clearly with reproducible steps, screenshots, and environment notes. My approach would be to methodically walk through the full organization lifecycle outlined in the issue—covering entry navigation, organization creation, settings updates, member invitations, archive/delete flows, sidebar navigation, and the public /org/[slug] profile—while validating UI state, API responses, permission checks, and edge cases like invalid slugs, expired invitations, and deep links. I will also monitor console errors, loading states, redirects, and toast/error handling, ensuring each flow behaves as expected and reporting any bugs, broken links, inconsistent state, or UX friction with precise reproduction steps so the team can quickly address them.