Access & Roles
The Kubuli admin console uses role-based access control. All accounts are managed by the platform team.
Roles
| Role | Capabilities |
|---|---|
| admin | Full access — all content types, user management, ingestion source configuration, system settings |
| curator | Content operations — review ingested items, create/edit/approve events, places, stories, and media |
Logging in
Navigate to the admin console login page:
- Local development:
https://localhost/admin/login - Production: Contact the platform team for the production URL
Use your assigned email address and password. The admin console uses Filament’s standard email + password authentication.
If you do not have credentials, contact the platform admin to create an account and assign a role.
Requesting access
Access requests go to the Kubuli platform team. Provide:
- Your name and organisation
- The role you need (admin or curator)
- The content areas you will manage (events, places, cultural stories, media)
Permissions summary
| Action | Admin | Curator |
|---|---|---|
| View the dashboard | ✅ | ✅ |
| Review ingested items | ✅ | ✅ |
| Approve / reject / promote items | ✅ | ✅ |
| Create events directly | ✅ | ✅ |
| Create and edit places | ✅ | ✅ |
| Manage cultural stories | ✅ | ✅ |
| Upload and manage photos | ✅ | ✅ |
| Manage ingestion sources | ✅ | ❌ |
| Manage users and roles | ✅ | ❌ |
| Monitor ingestion jobs | ✅ | ❌ |
| System settings | ✅ | ❌ |
Getting help
Contact the platform admin if you experience login issues, need a password reset, or need your role adjusted.