INKR Access


For INKR’s admins and hiring managers who need to onboard and manage hundreds of freelancers worldwide, INKR Access is an identity & access management system (IAM) that provides a centralized hub for managing access to all INKR enterprise products.

Unlike previous attempts at a user management system that requires various spreadsheets and calls, INKR Access features a user-friendly front-facing interface that walks new users through the onboarding process and allows them to provide their information directly to the system.

I spearheaded the initiative and single-handedly handled the end-to-end design of this product.

My Contribution

User Research
Product Strategy
Concepts & Ideation
Information Architecture
Enterprise UX/UI


1 designer
2 project managers
5 engineers



Problem Definition

To ramp up its catalog, INKR has been acquiring and localizing a lot of comic titles. As a result, the costs of producing and publishing comics pages have gone up significantly and need to be managed.

All cost-incurring activities at the time were tracked by project managers via spreadsheets, and as the volume increased dramatically, they found themselves spend more and more time with these book-keeping activities, as opposed to actual production.

Our first initiative was to establish an automatic and systematic way to track all cost-incurring activity on our current systems. However, we hit multiple roadblocks:

  • Each of our systems was using a different identity system. It will take a lot of engineering and resources to tell whether different accounts belong to the same person.
  • Some of the tools that our team was using such as Photoshop and Illustrator are third party and not cloud-based, therefore it’s impossible to track down its usage.

To solve this once and for all, the solution would be to centralized everything into one place, so that every activity can be properly tracked, audited, and accounted for. However, that would be too huge of an undertaking, a multi-year effort that we were not sure was going to be worth it. For a startup with limited resources, we were hesitant about such a big project.

Therefore, we set out to narrow down the scope to something more manageable. We believe that by achieving quick wins, we can kickstart the virtuous cycle and motivation for the longer-term goal.

One of the low-hanging fruit that we can pick is reducing the overhead cost of onboarding and managing external users on these systems.

Scope and Constraints

INKR Access is an enterprise product with the aim to provide a centralized hub to manage access to other enterprise products, in which new users will be able to register and follow a path to provide their information into the system, reducing the back-and-forth and overhead cost of onboarding new users.

We believe that this will have the immediate effect of cutting down a significant portion of the current overhead cost of onboarding new users.

The authentication and authorization service we are using is Auth0, with it also came specific requirements that need to be taken into consideration when designing, mostly in the login and admin experience.

Identifying Users

We’ve identified the people who need to gain access to CMS and LS as follow:

  • Content Partner Team Members: personnels from INKR’s signed partners that need to log into CMS and LS for various purposes (monitoring production/localization, financial reports, downloading relevant data, etc.)
  • Freelancers: hired freelancers that need to gain access to CMS and LS to carry out tasks assigned to them by their respective managers.
  • Admins: People who need to grant access to others and monitor their activities into CMS and LS.
  • Recruiters: Internal team members that need to grant access to their hired freelancer, such as content executives.
  • Finance: Internal team members that need to see immediate report of user activities on CMS and LS, such as accountants, managers, and so on.

Two of the above users that should get the most attention are Freelancers and CP Members, who are the most numerous. To reduce the repetitive tasks of onboarding these users into the system, we’ve narrowed down the user journeys that we want to tackle.

User Journeys

There are 2 types of users (CP Members and Freelancers) as well as 2 entry points that can happen: organic and invited. Therefore we identified 4 user journeys to cater for:

Freelancers Organic Journey

  1. Person finds their own way to INKR Access
  2. Person informs INKR Access they are Freelancer
  3. Person signs up using email password and authenticate themselves
  4. Person arrives to profile, get confused, might enter things randomly, can contact for access.
  5. Journey ends.

CP Member Organic Journey

  1. Person finds their own way to INKR Access
  2. Person informs INKR Access they are CP Member and wants to get access to their titles
  3. Person is asked which Organization they identify with
  4. Person chooses from a list of existing Organization: is told to contact organization admin. Journey ends.
  5. Person enters Organization name that does not exist: is told to contact INKR.
  6. Journey ends.

Freelancers Invited Journey

  1. Access Admins invites a person to sign up
  2. Person receives email that they are being invited to INKR with a specific role: INKR CMS user, INKR LS user
  3. Person clicks on email to open sign up flow on INKR Access, enter email and password to create a newa ccount
  4. Person arrives at the Access Profile, where they can edit their profile by providing necessary personal information, payment info, and documents such as NDA…
  5. Person see the tools they can access and get redirected to that tool to start working.
  6. Journey ends.

CP Member Invited Journey

  1. Person contacts Organization admin and expresses their need to access INKR Tools
  2. Organization Admin adds member to Organization on Access
  3. Person receives email that they are being invited to an Organization with what role: Member, Finance, Title Manager…
  4. Person clicks on email to open sign up flow on INKR Access: enter email, password and full name to authenticate
  5. Person arrives at the Access Profile: see which role they have in the organization, see other organization members, see what tools they can access, and recent acitivites.
  6. Journey ends.

Information Architecture

Based on the touchpoints illustrated above, I put down the screens and their required information.

Information Architecture

Wireframes & User Flows

While creating the information architecture, I also come up with rough wireframe to visualize the solution. Then I combine it with the overall flow to get this.

User Flows


Using Figma, I visualized the user journeys with the first rounds of mockups. The design system used is the Ant Design, the same one used across CMS and LS.

Organic Landing Flow
User Profile States


After meeting with other stakeholders from the infrastructure team, web front-end team, and project managers, we reached a consensus on multiple business rules and technical constraints that affects the design.

This feedback is used to update the design for several other rounds. I also elaborated the design for corner cases, empty states, error states,…

Finalized Design

After several rounds of iteration, the design is deemed fit for implementation. During implementation, I will need to be on standby to support if there is any problem related to the design.


After 1 month of implementation and adjustments, the system was launched to all users on the other two products, CMS and LS. There were some hiccups with the migration processes, services were out for a few days, and there was not a cohesive communication plan for the new releases, leaving many users confused. However, we eventually rectified these issues.

Early feedback from managers showed that INKR Access significantly reduced the effort that they have to do to onboard new users, freeing up their time for more important tasks.