Access & roles
You need a Ravelun account with the right permissions before you can use the admin panel.
Signing in
- Go to /admin in your browser.
- If you’re not signed in, click through to log in — you’ll come back to the admin panel afterwards.
- Once you’re in, you’ll land on the Dashboard or Routes page, depending on your role.
If you see an “access denied” message, your account doesn’t have admin permissions yet. Ask your Ravelun contact or organisation owner to grant access.
The three roles
Ravelun admin
Full access to everything. Typically used by Ravelun staff.
- See stats for the whole platform
- Create routes for Ravelun or assign them to a partner organisation
- Publish routes to the main Ravelun catalogue
- Manage users, partners, discount codes, and platform settings
Partner
For destination organisations — tourist offices, museums, regional brands, and similar.
- See your organisation’s routes, orders, and commission on the dashboard
- Publish routes on your brand page (not the global Ravelun catalogue unless Ravelun does that for you)
- Customise your logo and colours
- Invite team members (owners only)
Editor
Content creators who build routes but don’t run the organisation.
- Work on routes you’ve created (or routes in your organisation, if you’re linked to one)
- Save drafts and mark routes as ready for review
- Cannot publish a route live — a partner or Ravelun admin does that final step
- Cannot delete a route that’s already live
What you’ll see in the menu
Not everyone sees the same menu items. That’s normal — you only see what’s relevant to your role.
| Menu item | Admin | Partner | Editor |
|---|---|---|---|
| Dashboard | ✓ | ✓ | — |
| Routes | ✓ | ✓ | ✓ |
| Partners | ✓ | — | — |
| Team | — | ✓ | — |
| Branding | — | ✓ | — |
| Orders | ✓ | ✓ | — |
| Users | ✓ | — | — |
| Coupons | ✓ | — | — |
| Voice & AI settings | ✓ | — | — |
Who can edit which route?
- Ravelun admins can edit any route.
- Partners can edit routes belonging to their organisation.
- Editors can edit routes they created themselves (unless they’re part of a partner org, in which case they work on that org’s routes).
Next step
How to get around the panel — menus, layout, and language switching.