Permissions

Launched: March 2025

Flexible, adaptable permissions for any user and team

At Gripp, we work with clients of all sizes, from small teams of around 10 people to large organizations with over 500 employees. With so many staff members joining and leaving, some clients began requesting more control over what their employees can see. This led to the need for a permissions feature with different access levels to help them manage visibility across their teams.

Team

  • Sole Product Designer (Me)
  • 1 Product Manager
  • 2 Engineers

Client Demand

35%

of clients requested access control to manage seasonal workers.

Client Satisfaction

85%

satisfaction among adopting clients after launch.

Context

How did the previous invitation process work?

In the old design, tapping the orange '+' button instantly revealed an invitation code. Anyone could scan and join, gaining full access to all activities, groups, and assets. It felt like a new employee seeing everything from finance to HR at once. For the company, this exposed too much, and for employees, it wasn’t clear where to focus.

Gripp invite screen showing QR code to invite others

Problem

Temporary workers and visitors often join farms for short-term tasks or specific equipment, but they can still see everything happening on the farm. Farmers need a way to limit access so people only see what's relevant.

Rob, Manager

I manage teams and employees, but right now everyone has full access, and it’s hard to control.

Mariah, Full-time Staff

I’ve worked here for several years and sometimes onboard new members for packing line work.

Devin, Temporary Worker

I’m a temporary worker who works across multiple farms and sometimes switches between them.

Danny, Farmer

It’s a family-run farm, and I want a simple way to share access with others. Privacy isn’t a concern for me.

Feature Request

Hey Gripp, can we have permission to invite people to specific groups only, instead of the whole workplace? – requested by 4 clients in January.

Interview - Service Blueprint

After interviews, I validated these role insights by reviewing companies of different sizes and found both shared patterns and variations.

After reviewing our client personas, I realized that not all farms have the same staffing structure. Some don’t have managers, long-term employees, or seasonal workers/mechanics. Smaller farms may just be run by the owner together with friends or family.

Company Size: ~ 10 ~ 200 ~ 1000
  • Rob

    Manager

    I manage teams and employees, but right now everyone has full access, and it’s hard to control.

    Goals:

    Be able to see who has which access and manage everyone’s permissions based on their role.

    Frustrations:

    Too much access makes it easier to make mistakes and creates confusion around responsibilities.

  • Mariah

    Full-time Staff

    I’ve worked here for several years and sometimes onboard new members for packing line work.

    Goals:

    Quickly and clearly onboard new packing line staff so they can start working confidently and correctly.

    Frustrations:

    Full access makes it harder to guide new staff’s focus during onboarding.

  • Devin

    Temporary Worker

    I’m a temporary worker who works across multiple farms and sometimes switches between them.

    Goals:

    Move efficiently between farms without losing access to tasks or any information, so I can work with confidence.

    Frustrations:

    When switching between farms, I sometimes forget what tasks I’ve completed or need to do next.

  • Danny

    Farmer

    It’s a family-run farm, and I want a simple way to share access with others. Privacy isn’t a concern for me.

    Goals:

    When friends or family members want to help out, I want to quickly share access with them.

    Frustrations:

    Right now, everything is working perfectly for me, and I’m not feeling any frustration.

Ideation

After understanding the needs of different companies and personas, I reviewed our current flows and the key pages affected.

With a clear understanding of the personas and business goals, I explored solution concepts aligned to user needs. After defining the ideal solution, I created task flows for each persona and evaluated the key pages affected across the product.

Task flows for Manager Admin, Long-term staff General, and Temporary workers Restricted personas
Before — Allan Brothers mobile activity feed

Before

Design Choice - Notification

To help temporary workers stay on top of tasks across different workplaces, I designed notifications that alert them whenever they are mentioned in any workplace.

After — All Activity mobile feed

After

Teams Feedback – All Activity

After discussing with the team, we decided to include an All Activity option, which not only lets users stay on top of multiple workplaces but also view their past completed tasks.

Before — account type roles Manager, Worker, Viewer

Before

Design Choice - Permission Flexibility

Originally, I designed the system so that each company has the flexibility to set different access levels, as each company has different needs.

After — account type roles Admin, General, Restricted

After

Feasibility Test - Fixed Permissions

However, considering the timeline and scope, we decided that for the MVP, permissions will be fixed for all companies, since giving flexibility to set them would require extra time.

Before — warranty registration detail screen buried context

Before

Design Choice - User-Friendly Names

When designing the names for different permission account types, I chose roles like Manager, Worker, and Viewer, as these are more user-friendly for clients.

After — photo, status, and action in one card

After

Design Choice - Content Design

When reviewing roles with different clients, I noticed that not every client uses the same names like Manager, Worker, and Viewer. Even when they do, the permissions for these roles often differ.

Reflection

Business v.s. UX Tradeoff

I often found myself acting as the intermediary between clients and engineers. In the first few projects, I struggled to convince clients of the value of UX due to a limited number of interviewees caused by budget constraints. However, after gaining some experience, I realized that engaging stakeholders at every stage of the project makes a significant difference. They become more receptive and are able to put themselves in the users' shoes, providing valuable feedback.