Certificate Authority

No prototypes due to NDA.

But I'll tell what I can because it was a really great project.

I started this project as a Frontend Engineer closely collaborating with UX and Dev Teams. In 2 years, I decided to pursue my passion and stepped up when our UX Designer was leaving. For some time, I was actually doing both front-end and design.

Type

Long-term internal project

Role

Frontend Engineer, UI/UX Designer

Timeline

Oct 2010-Aug 2014

It's a service for certificate authority (CA) that issues electronic signatures (certificates) for individuals and companies. Electronic certificates are to report tax data to State Tax Authority, to participate in electronic auctions, and to do other business-to-government things.

Issuing electronic certificates consists of several phases that include 6 groups of people to conform the legislation. Most of these groups are internal users. Every day, I got feedback from all of them, so I've learned how to juggle and prioritize tasks.

The scheme below presents how the whole process looks like.

PRIVATE CABINET

An interface for clients. They fill up their data, send requests for certificates, and store certificates online.

REGISTRATION CENTER

An interface for specialists who communicate with clients. They meet clients offline, take their docs, request for certificates and track a process online.

CERTIFICATE AUTHORITY

An interface for operators who check requests. They verify clients' scans and personal data.

DOCUMENTATION CENTER

An interface for specialists who receive paper documents. They compare docs to electronic copies.

BIG BROTHER

An interface for very powerful people :) They have a full access to everything and solve the most difficult problems.

TECHNICAL SUPPORT

An interface for specialists who help clients in difficult situations.