Manual for organizers
Turn an event plan into a controlled sales and entry operation.
Entriza keeps the organizer, venue, line-up, ticket inventory, payments and entrance connected while preserving separate permissions. This manual follows the launch order shown in the organizer dashboard. Complete the legal seller and payment setup before opening sales, and keep event information accurate in all four supported languages.
Create the organizer workspace and assign responsibilities
Start with a personal account, then create or join the organizer workspace that will operate the event. The workspace represents the event team, while the connected seller is responsible for the ticket sale. A person may also have a DJ or location role, but those areas keep separate permissions. Give each colleague only the access needed for events, locations, rewards, guest lists, scanning or finance-related work.
What to do
- Use the real public organizer name and a monitored contact address.
- Confirm who can publish, manage inventory, answer refunds and supervise entry.
- Remove access promptly when a team member no longer works on the event.
Connect the seller and payment account
Connect the organizer's Stripe account from the setup flow and complete the verification requested by Stripe. Ticket payments are processed for the organizer identified on the event page. Entriza does not need raw card data or copies of payment identity documents. The launch checklist will remain incomplete while the payment account cannot receive the intended charges, so resolve any restriction before announcing that tickets are on sale.
What to do
- Enter business and payout details directly in the Stripe-hosted process.
- Return to the organizer dashboard and confirm the displayed verification state.
- Name the person responsible for payment disputes and refund decisions.
Choose the venue and build the public event page
Search existing locations before creating a new one. Using a venue for an event links the place but does not transfer control of its profile. Add the event name, description, date, start and end time, age rule, imagery and the practical information guests need. Review English, Greek, German and Russian before submission. If automatic translation is used, treat it as a draft and correct names, music terms, access rules and local wording yourself.
What to do
- Check the map pin, city and venue name against the real entrance.
- Explain the format, final entry conditions and important accessibility information.
- Add the organizer, venue and line-up as separate linked identities.
Configure inventory, prices and optional tools
Create ticket types with a clear name, description, capacity, price and maximum quantity per order. Use price phases and promo codes only when their start, end and limits are easy to explain. Table packages, guest-list places and rewards are separate operational products and should not silently consume the wrong inventory. A reward campaign needs a real budget, a paid-referral threshold, a per-user limit, an redemption period and a staffed reward station.
What to do
- Reconcile the sum of saleable capacities with the venue's approved operating limit.
- Test the wording of every ticket option with someone who did not configure it.
- Set reward and guest-list limits before sharing invitations or referral links.
Complete review and publish deliberately
Use the launch checklist as the source for missing setup. Confirm seller, payment state, venue, timing, ticket stock, refund contact and all customer-facing translations. Submission sends the event through the configured review path; a draft is not publicly saleable. After publication, share the canonical Entriza event URL so guests receive current details rather than an image that cannot be updated.
What to do
- Preview the page on a phone and follow every organizer, venue and line-up link.
- Run through checkout and entrance procedures with the responsible team before sales grow.
- Publish only when the team can answer support and refund questions.
Operate changes, customers and reporting
Keep the event page current after publication. Material changes to date, venue, city, ticket status or cancellation state create notifications for affected users. Refund requests remain structured cases until the responsible decision and payment action are complete. The dashboard combines orders, paid referrals, admission and other operational counts so the team can act without exporting unnecessary personal data. Record the reason for exceptional decisions and use platform support when a payment, credential or permission state is unclear.
What to do
- Assign one owner for each material event update and customer message.
- Review sales and entrance numbers without sharing raw guest lists in group chats.
- After the event, close operational access that is no longer required and retain only required records.
Organizer launch checklist
0 of 5 completed
The checklist remembers your progress in this browser.
Manual for organizers
Common organizer questions
Why can I not publish the event?
Open the launch checklist and follow the first incomplete item. Typical blockers are seller verification, missing venue or ticket data, incomplete translations, permissions or a pending review. Do not create a duplicate event to bypass the blocker.
Can I edit a venue or DJ profile because it appears on my event?
No. An event link does not grant control of another profile. Invite the DJ, ask the location owner to update its profile or use the claim process when you can prove that you represent the identity.
What should happen when the event is postponed or cancelled?
Update the event state and customer-facing details promptly, document the decision, review the applicable refund route and answer affected support cases. Do not rely on a social post as the only notice to ticket holders.