Simran Jobanputra KumarBoston, MA
← All work

Sight Machine · Enterprise · B2B2B

Role-based access for factory data

As the only designer, I designed role-based access for Sight Machine’s manufacturing platform in 8 weeks. It ended up being one of the main reasons two Fortune 500 machine makers signed on.

2Fortune 500 machine makers signed
8 weeksfrom research to production
Adding members to a team: search all users on the left, see who is selected on the right

The challenge

Sight Machine sells its analytics software bundled with machine makers’ equipment. Every factory a machine maker sold to got its own Sight Machine environment, so machine makers juggled a separate login for each customer.

Moving everyone into one shared environment meant we had to solve for access, since each factory could only see its own data while the machine maker needed to see across all of them.

Solution

I designed one settings home where machine makers can create a team for each customer, add users, and set exactly which plants and data each team can see.

Access control now lives alongside the rest of the platform settings, so admins can manage everything in one place.

Process

01

Co-design with machine makers

I tested a few concepts with machine makers, including customer groups, access cards, flippable team cards and a pop-over for adding users. These sessions also showed us where the flow between pages broke down.

Co-design concept: a list of customer groups and a form to create one
Customer groups
Co-design concept: an access card with edit, view or no access for each page, and plant access
Access cards
Co-design concept: flippable cards with a team on the front and its members on the back
Flippable cards for editing teams
Co-design concept: a pop-over for creating a new user with role and plant access
A pop-over for adding users
02

One home for settings

Before, unrelated settings were all on one page and there were no user settings at all. I created a settings landing page that sends you to profile, users, teams, feature toggles and more.

Before and after: settings scattered across the old menu and a crowded platform settings page, then one Settings item and a settings home
03

Creating a team

Admins can name the team in place, add members with contextual search, and see who’s selected before applying changes.

The design

Teams, members, and permissions in one place.

Machine makers build teams for each customer, assign roles and permissions, and manage every group from a single environment.

Settings home: usage stats, colored cards for profile, teams, users, feature toggles and more, and recent changes
Settings homeOne landing page for user and platform settings, with a little color.
Teams page listing each team and its member count
TeamsCreate, edit and delete teams without leaving the page.
Adding members to a team with search and a selected list
MembersAdd users with contextual search and clear selection states.
Users summary table with status, roles, teams and last active
Users summaryEvery user’s permissions and access in one table, plus new profile creation.

More case studies

All work →
RayBuilding trust in an AI trainerClarifying Ray’s value from day one, leading to a 20% increase in subscriptions.
HopperRedesigning hotel shoppingSimplifying Hopper’s hotel list, leading to a 14% increase in conversion.
RayRay’s brand and design systemBuilding the Ray app’s first brand system, including motion design and Ray’s voice.