Loading
Loading
Loading
Events are the core of Ascend.
Last updated: 2026-02-04
Make the event visible to participants (based on visibility).
Publishing makes the event discoverable and opens participant access according to visibility settings.
Hide the event while keeping it editable.
Draft mode removes participant visibility but keeps your data intact for edits.
Mark the event as inactive for records.
Archived events are treated as inactive and are hidden from normal flows.
Display name shown on event pages and listings.
Use a clear, recognizable name. It appears in navigation, cards, and invites.
Unique URL identifier for the event.
Lowercase letters, numbers, and hyphens only. Used in event URLs.
Hackathon, Ideathon, or Generic classification.
Used for filtering and to set participant expectations. Generic events are not classified as hackathons or ideathons.
Optional summary shown on the event page.
Use this to explain the event at a high level. If you do not see a separate description field, use the hero subtitle.
Primary headline shown in the event hero.
Keep it short and action-focused to set the tone.
Supporting line shown under the hero title.
Use one sentence to describe the event or target audience.
Wide banner image used on the event header.
Choose a wide image that represents the event. Recommended for hero sections and previews.
Controls who can discover the event.
Public Listed appears in listings, Public Unlisted requires a link, and Private restricts access.
How participants can join the event.
Open allows immediate join, Request requires approval, Invite-only restricts access.
Let users request to join when Join mode is Request.
Only available before the event starts and when Join mode is Request.
Maximum number of participants per team.
Used to enforce team size limits across creation and invites.
When registration begins.
Participants can join after this time if visibility allows.
When registration ends.
After this time, new participants can no longer register.
When the event begins.
Participants can start building and submitting after this time.
When the event concludes.
Submissions should be finalized by the submission due time before the event ends.
Deadline for final submissions.
Teams can edit until this time unless the event is locked earlier.
When submissions become visible to viewers.
Often set after judging ends so judges can score before results go public.
When judges can start scoring submissions.
Judges can access scoring tools after this time.
When judging becomes read-only.
After this time, judges can no longer edit scores or notes.
Optional end time for judging.
Use this if your judging window has a hard cutoff.
Venue name shown on event pages.
Use the building or venue name (for example, UCSD Jacobs Hall).
Street address for in-person events.
Displayed to participants for navigation and check-in.
Optional location details or instructions.
Add parking info, room numbers, or arrival instructions.
Link to a map for the event location.
Paste a share link from Google Maps or another map provider.
Rules and guidelines shown on the event page.
Markdown is supported for headings, lists, and links.
Judging rubric shown to participants and judges.
Use Markdown to explain how submissions will be scored.
Require images with each submission.
If enabled, teams must upload images to submit.
Require a demo video URL with submissions.
If enabled, teams must add a video demo link to submit.
Maximum number of participants per team.
Used to enforce team size limits across creation and invites.
Prevent team membership changes after the event starts.
Helpful for fairness once the build period begins.
Send a direct invite to a specific email address.
Creates an email invite with a join link and optional message.
Optional message included in the invite email.
Use this to add context or instructions for the recipient.
Limit how many times a link invite can be used.
Helpful when sharing a link with a small group.
Date and time the invite link expires.
After this time, the link is invalid and cannot be used.
Internal note for your team.
Not visible to recipients. Use it for tracking why the invite was created.
How long the invite link stays valid.
Set an expiry window in minutes to reduce stale invites.
View and manage teams in this event.
Use this section to review teams and take administrative actions.
View and manage participants in this event.
Remove participants or review member details when needed.
Choose how rubric scoring is enforced.
Required means judges must score categories before finalizing. Optional means categories are available but not required. None disables category scoring.
Maximum points per rubric category.
Use 10 for finer scoring or 5 for a simpler rubric.
Category name shown to judges and participants.
Examples: Innovation, Impact, Technical Difficulty.
Controls display order of rubric categories.
Lower numbers appear first.
Optional guidance for scoring this category.
Explain what judges should look for when scoring.
Percent weight for this category in the final score.
All category weights should add up to 100.
Track name shown to participants.
Examples: AI, Health, Climate, Fintech.
Controls display order of tracks.
Lower numbers appear first.
Optional summary for the track.
Use a short line to describe what projects belong in this track.
Optional questions participants answer before joining.
Use registration questions to collect details during event join. Answers are visible to event staff.
Prompt shown to participants.
Write a clear question so participants know exactly what to answer.
Expected answer format for the question.
Choose Text, Email, Link, True/False, single-select, or multi-select based on the response format you need.
Optional guidance shown under the question.
Use helper text to clarify what a good answer should include.
Require participants to answer before joining.
Enable this when a response is mandatory for processing join requests.
Answer choices for single-select and multi-select questions.
Add clear options for selection-based questions. Participants can choose one or multiple options based on question type.
Award name shown on the winners page.
Examples: Best Overall, Most Innovative, Best Design.
Controls display order of awards.
Lower numbers appear first.
Optional description shown with the award.
Use this to explain what the award recognizes.
Allow this award to be assigned to more than one team.
Useful for categories like Community Choice or Honorable Mention.
Find an existing sponsor by name or website.
Search the global sponsor library to avoid duplicate records.
Pick a sponsor to link to this event.
This creates an event-specific sponsor link with its own settings.
Sponsorship tier used for ordering and styling.
Use tiers like Title, Platinum, or Gold to reflect level of support.
If enabled, the sponsor is shown on the event page.
Disable to hide the sponsor without deleting the link.
Override the sponsor name for this event.
Use this if the sponsor prefers a different display name.
Controls the display order within the sponsor list.
Lower numbers appear first. Leave blank to use defaults.
Short event-specific description for the sponsor.
Shown alongside the sponsor on event pages or sponsor sections.
Upload a logo specific to this event.
Overrides the global sponsor logo for event-specific branding.
Adjust existing staff roles or remove access.
Staff access is separate from participant membership.
Invite judges or staff via email or link.
Use invites to grant staff roles without sharing admin credentials.
Short headline for the announcement.
Shown in announcement lists and notification emails.
Main announcement content.
Provide details, links, or action items for participants.
Email the announcement to all participants.
Enable this to send notifications outside the app.