Welcome to the ERADIANT documentation
Welcome to the ERADIANT documentation!
Here you'll find everything you need to work with our event management platform.
🚀 Start here
New to ERADIANT? Start with the Introduction – there you'll learn:
- what ERADIANT is and what you can use it for
- how ERADIANT is structured (modules, submodules, components)
- how the documentation is organised and how to find your way around
📚 Documentation structure
The documentation is divided into several areas:
Getting started
- Introduction: Overview of ERADIANT and this documentation
- User account: Set up your access
- Important terms: Key definitions
- Main functions: Tables, blocks and core UI elements
General
- Use cases: Typical ways to use ERADIANT
- Solved problems: Which challenges in event management ERADIANT helps you solve
- User stories: Examples of how different users successfully work with ERADIANT
Usage & processes
- Usage & processes: Overview of tips and end-to-end processes
- Working with event mailings: Recommendations for content, dispatch, and recipients
- Invitation mailing process: Invitation campaign step by step
- Program website process: Publish program on the event website
- Networking process: Ticketing sync, locations, time slots, code delivery, and testing
Troubleshooting
- Troubleshooting: Step-by-step help for common problems
- FAQ: Answers to frequently asked questions
Web app
- Web app overview: Modules and areas of the browser interface
- Event module: Events, program, website, networking, mailings
- Contact module: Contacts, institutions, leads
- Ticketing module: Ticket sales, orders, check-in
- Voting module: Votes and elections
- Organization module: Members, email dispatch, payment providers
Check-in apps
🔍 Quick links
- Installation & account – set up your first access
- Event module – jump straight to events
- Ticketing module – jump straight to ticketings
- Contact module – jump straight to contacts
🛠️ Help
- Contact support – if you can't find a solution in the docs
💡 Tip
Use the left sidebar to navigate through the documentation.
The structure follows the logic of the platform: modules → submodules → components.