The platform

ID card management software, end to end

ID Portal is the platform behind every card SecureID issues. It takes a cardholder from a photograph on their phone to a printed, encoded, registered credential — and to a digital ID in their wallet — without anybody re-keying a name.

Walk through it

Six parts of the platform. Choose one to see what it does.

One record per person, for as long as they are with you

Every card, photograph, order and digital pass hangs off a single cardholder record. A student who loses a card in first year and graduates in their fourth has one record, one history and one verification trail — not four unrelated print jobs.

  • Bulk import from a spreadsheet, with column mapping and a preview before anything is written.
  • Roles and scope so a faculty administrator sees their people and nobody else's.
  • Full audit trail — who changed what, and when.
  • Configurable retention for photographs, and cardholder data requests handled in the platform.
Underneath

The parts nobody demos, that decide whether you keep it

Tenant isolation

Each institution's data is separated at the database level as well as in the application, so one organisation cannot read another's cardholders.

Audit logging

Every mutation records who did it, to what, and what changed. “Who revoked this card, and when?” has an answer.

Single sign-on

SAML and OpenID Connect, so staff use the credentials they already have and access ends when their account does.

Two-factor authentication

Time-based one-time codes with backup codes, for the accounts that can issue and revoke credentials.

Retention & privacy

Photo retention periods are configurable per organisation, rejected photos are cleared sooner, and cardholder data requests are handled in the platform.

Webhooks & API

Issue, revoke and reconcile from the systems you already run, with delivery retried and recorded.

Common questions

Frequently asked

Is this one system or several?

One. Cardholder records, photo collection and review, card design, ordering, print production, digital ID issuance, verification and billing are all the same platform, sharing one cardholder record and one audit trail.

Can different departments manage their own cardholders?

Yes. Access is scoped by organisation and controlled by role, so a faculty or campus administrator sees their own people and nobody else's, while a central card office sees everything.

What happens when somebody leaves?

Revoke their card, their digital ID, or both. A revoked digital ID is struck through on the phone; a revoked card stops verifying immediately. Their record and history stay intact for audit.

Does it integrate with the systems we already run?

Cardholders can be imported from a spreadsheet export, and the platform provides webhooks and an API so issuance can be driven from your student management or HR system. Single sign-on is supported through SAML and OpenID Connect.

See it against your own process

Tell us how you issue cards today and we will show you what this looks like for your institution. No obligation, and no sales script.