Owner / Venue Operator
You are owner, managing director, or formally authorized and need profile, promo, and club-plan control for the venue.
How-to · Verification Flow
Become owner or event manager without verification chaos.
This guide follows the real business flow: choose role, prepare proof, submit request, interpret status, and move cleanly into operations after approval.
Owner: club claim + venue rights
Event Manager: event rights without venue claim
Step 1
Select the correct role first.
Event Manager / Agency / Collective
You run events and need event execution rights without taking full owner control of the venue.
Rule: if your primary scope is venue profile and club promotion, choose owner flow. If your primary scope is event execution, choose event-manager flow.
Step 2
Prepare and submit proof correctly.
A
Owner proof
Provide at least one strong proof item, ideally two independent sources (for example company relation + domain/profile signal).
B
Domain/meta-tag option
If used, keep the verification marker visible on the official domain until approval is final.
C
Event-manager proof
Document your project relationship and practical event authorization clearly.
Clean proof packages reduce approval time significantly.
Step 3
Understand status and next action.
| Status | Meaning | Next Action |
|---|---|---|
| Pending | Review is ongoing | Keep submitted signals stable, avoid contradictory updates |
| Approved | Role unlocked | Start plan setup and event workflow immediately |
| Rejected | Proof is insufficient or inconsistent | Fix root cause, improve proof quality, resubmit once |
After approval
Move into clean operations fast.
- Assign role ownership internally (who owns plans, who owns event publishing).
- Audit business profile consistency.
- Define promotion strategy per calendar phase.
Review Criteria
What verification checks actually evaluate.
- Identity logic: applicant, brand, and contact route must align.
- Role logic: owner only with legal representation rights, event manager with operational event responsibility.
- Proof quality: at least one strong evidence item, ideally two independent signals.
- Consistency: website, Instagram, domain email, and documents must not conflict.
Timeline and Escalation
Avoid verification loops and resubmission chaos.
- Submit once with a complete package instead of many partial updates.
- Pending means active review, not automatic failure.
- If rejected, resubmit only after root-cause corrections are complete.
- For technical blockers, contact support with timestamp, role, and exact steps.