Frequently asked questions
Straight answers about security, voting, roles, and how institutions use Electra.
What is Electra?
Electra is a secure digital election management platform for universities and colleges. It covers student verification, candidate management, one-time voting codes, turnout monitoring, and official result publication.
Who can use Electra?
Institutions (universities and colleges) and their designated roles: institution admins, voting managers, candidates, and student voters. Platform super admins manage multi-tenant oversight.
How do students vote securely?
Students authenticate with their institution ID, student code, and a one-time voting code issued for the active election. Codes are hashed, can expire, and are single-use. Database constraints enforce one vote per student per position.
Can results be seen while voting is open?
Live views focus on aggregate turnout, not individual ballot choices. Official results are published as controlled snapshots after the election, according to institutional policy.
Does Electra support multiple positions and running mates?
Yes. Elections can include multiple positions. Running mates can be paired across positions, with optional auto-select behaviour configured by the voting manager.
How is data isolated between institutions?
Electra uses shared-schema multi-tenancy with institution_id on tenant data, plus middleware and policies so users cannot access another institution’s records.
Is there an audit trail?
Yes. Privileged and election-critical actions can be recorded in audit logs for accountability and post-election review.
How do we get started?
Enter your institution ID on the Electra homepage to access your institution portal. New institutions are provisioned by platform administrators according to your deployment process.
Still need help? Contact Electra →