Different badges answer different questions
Hooj uses verification types instead of treating every badge as a universal statement of trust. The current system distinguishes verified users from verified organizations, and the interface can identify the type when a badge is pressed.
A user completed the supported verification flow for an approved school email domain.
Hooj reviewed an organization request and approved the organization based on submitted context and evidence.
Future verification types may represent other specific credentials or affiliations. A new type should explain what was checked rather than changing the meaning of an existing badge silently.
How user verification works today
For a live campus, signup requires an email domain approved for that school. Hooj sends a six-digit verification code to that address. The user account is created as verified only after the correct code is submitted before the signup session expires.
- Select a live school in Hooj.
- Enter an email using one of that school's approved domains.
- Receive the verification email and enter the six-digit code.
- Complete the profile after the account is created.
If the school is not live, use Get the app to join the waitlist. Do not select another school or use an address you do not control.
What the user badge does and does not mean
The current user badge means the person demonstrated access to an approved school email address during Hooj's verification flow. It helps establish campus context.
It does not mean Hooj has:
- Reviewed a government-issued identity document or completed a background check.
- Confirmed current enrollment, graduation status, employment, age, qualifications, or authority beyond the supported email check.
- Approved the user's posts, listings, events, messages, organizations, or conduct.
- Guaranteed that a transaction, meetup, ticket, event, or relationship will be safe.
Verification does not exempt an account from reporting, blocking, moderation, or enforcement.
Who can request organization verification
An organization must already exist in Hooj. Only the organization owner or an admin with the current verification capability can open and submit the verification request.
Being a member, moderator, event manager, content contributor, follower, or organization-chat participant does not by itself allow someone to request verification.
Verification is appropriate when the organization page represents a genuine group and the requester can provide a credible official source or other evidence connecting the Hooj page to that group.
Prepare the organization before requesting
Complete the organization page so Hooj can compare the request with a coherent public identity. Before submitting:
- Use the organization's real name and appropriate organization type.
- Add an accurate description, avatar, cover image, and relevant links.
- Confirm that the owner and admins are current and authorized.
- Remove misleading affiliations, outdated leadership claims, and copied branding you may not use.
- Make sure the official source uses enough matching information for a reviewer to connect it to the Hooj organization.
A polished page alone is not proof. Verification depends on the evidence and context, not visual quality or follower count.
What the organization request asks for
The requester's real role or relationship to the organization.
A required official website or credible public source associated with the organization.
An optional school or campus directory page that independently identifies the organization.
Optional concise context explaining the organization, your authority, name differences, or why the evidence is relevant.
An optional additional link containing useful verification evidence. The current flow accepts a URL rather than a direct document upload.
Do not place passwords, private keys, complete financial information, government ID numbers, or unrelated personal information in a supporting note or public evidence link.
Submit from organization management
Open the organization, choose Manage, and open its verification area. Eligible owners and admins can view the latest state and submit a request.
An organization cannot submit another request while the latest request is pending or in review. If Hooj requests more information, update and resubmit the existing request rather than creating a new organization.
An organization that is already verified cannot submit another verification request unless its verification state changes.
Understand each request status
No organization verification request has been submitted.
The request was submitted or resubmitted and is waiting for review.
A Hooj reviewer is evaluating the request and available evidence.
The reviewer needs clearer, corrected, or additional information. The owner or admin can update and resubmit the request.
The request passed the current review and the organization can display the verified organization badge.
The submitted request did not establish verification under the current review. A badge is not granted.
How organization review works
Hooj staff may compare the page, requester role, official URL, campus directory, supporting note, evidence link, organization history, and other relevant information. Hooj may approve, reject, move the request into review, or ask for more information.
Review timing can vary with evidence quality, request volume, school availability, safety concerns, and the need for clarification. Hooj does not promise approval or a particular review time.
False evidence, impersonation, misleading claims, or attempts to manipulate review may lead to rejection, organization suspension, or account enforcement under the Community Guidelines.
What the organization shield means
The verified organization shield indicates that Hooj approved the organization through the current organization-verification review. It can help distinguish a reviewed organization page from an unverified page with a similar name.
It does not mean Hooj:
- Endorses the organization, its leaders, politics, beliefs, posts, events, or members.
- Confirms official recognition by every school, government, employer, national chapter, or outside institution.
- Guarantees event safety, ticket validity, financial condition, legal compliance, or member conduct.
- Reviews every future change or piece of content before publication.
Tap or press the badge in Hooj to view the verification type and context shown by the interface.
Statuses that are not verification badges
Ambassador status reflects participation in Hooj's campus growth program. It is not identity, school, organization, safety, or professional verification.
Stripe onboarding and payment readiness relate to payment-account requirements. They do not verify listings, events, organizations, or conduct.
Owner, admin, moderator, and member access describe permissions inside one organization. They do not establish external credentials.
Hosting, managing, RSVPing, purchasing, or checking in describes event activity, not general verification.
Keep verification accurate
Users and organization leaders must keep names, affiliations, links, leadership, and supporting information accurate. Hooj may request reverification, change a verification type, or remove a badge when information becomes outdated, misleading, compromised, transferred, or inconsistent with current requirements.
Verification may also be removed or the account restricted for fraud, impersonation, serious policy violations, compromised access, or attempts to evade enforcement.
To question a badge, report the relevant account or organization in Hooj. For your own verification problem or an organization review issue, contact support@hooj.app with the account or organization and concise supporting context.