Creating a Multi-Dimensional Permissions System
COMPANY
Cube
ROLE
Product Design Lead
Product Design Lead
INDUSTRY
Fintech
TOOLS
Figma
PROJECT TYPE
Feature Overhaul
>
0.1
About Cube
Github for Finance Folks
d[lzkzdl[zkd[lkzd[lvzkdv[lzkvl[zkvzl[dvkzl[vkzl[vzkd[vlzkdv[lzdkvl[zdkvl[zdvkzdlvkzd[lvkzd[vlkzdv[lzkdvl[zdkv[lzdvkzd[lvk
>
0.1
About Cube
>
0.1
About Cube
>
0.2
The Problem
>
0.2
The Problem
>
0.2
The Problem
>
0.3
The Solution
>
0.3
The Solution
>
0.3
The Solution
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
#1 on Eclipse
Reusable Roles
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and even copy roles to speed up setup for new hires.
To reduce friction during migration, we kept the original 3 canned roles—but made them editable. And to simplify ongoing management, we collapsed the setup into a 3-click flow: Pick Role → Set Dimensions → Apply Permissions.
The result? A flexible, scalable system that works for everyone—from lean startups to global finance teams. Admins get control, users get autonomy, and permission-related support tickets dropped by 80%.plainer
>
0.4
Results
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
#1 on Eclipse
Reusable Roles
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and even copy roles to speed up setup for new hires.
To reduce friction during migration, we kept the original 3 canned roles—but made them editable. And to simplify ongoing management, we collapsed the setup into a 3-click flow: Pick Role → Set Dimensions → Apply Permissions.
The result? A flexible, scalable system that works for everyone—from lean startups to global finance teams. Admins get control, users get autonomy, and permission-related support tickets dropped by 80%.plainer
>
0.4
Results
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
#1 on Eclipse
Reusable Roles
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and even copy roles to speed up setup for new hires.
To reduce friction during migration, we kept the original 3 canned roles—but made them editable. And to simplify ongoing management, we collapsed the setup into a 3-click flow: Pick Role → Set Dimensions → Apply Permissions.
The result? A flexible, scalable system that works for everyone—from lean startups to global finance teams. Admins get control, users get autonomy, and permission-related support tickets dropped by 80%.plainer
>
0.4
Results
THE WORK
Explore each artifact — click a card to view
UXR Summary
After interviewing 4 users, 2 support reps, and reviewing our feature request board, all sources pointed to the same core problems.
Competitive Analysis
4 companies analyzed in FP&A — the result shows a simple, intuitive roles-based permissions system would stand out in FP&A
>
1.0
Empathize
UXR Summary
Competitive Analysis
THE WORK
Explore each artifact — click a card to view
UXR Summary
After interviewing 4 users, 2 support reps, and reviewing our feature request board, all sources pointed to the same core problems.
Competitive Analysis
4 companies analyzed in FP&A — the result shows a simple, intuitive roles-based permissions system would stand out in FP&A
>
1.0
Empathize
UXR Summary
Competitive Analysis
THE WORK
Explore each artifact — click a card to view
UXR Summary
After interviewing 4 users, 2 support reps, and reviewing our feature request board, all sources pointed to the same core problems.
Competitive Analysis
4 companies analyzed in FP&A — the result shows a simple, intuitive roles-based permissions system would stand out in FP&A
>
1.0
Empathize
UXR Summary
Competitive Analysis
>
2.0
Define
Levelset Workshop
Hypothesis
>
2.0
Define
Levelset Workshop
Hypothesis
>
2.0
Define
Levelset Workshop
Hypothesis
>
3.0
Ideate
Blue sky Story Mapping
>
3.0
Ideate
Blue sky Story Mapping
>
3.0
Ideate
Blue sky Story Mapping
>
4.0
Design
IA Work
UXUI Progression
Hi-Fi Prototypes
>
4.0
Design
IA Work
UXUI Progression
Hi-Fi Prototypes
>
4.0
Design
IA Work
UXUI Progression
Hi-Fi Prototypes
>
5.0
Research and Iterations
UXR Results
Designing Data Roles
Final UXUI
>
5.0
Research and Iterations
UXR Results
Designing Data Roles
Final UXUI
>
5.0
Research and Iterations
UXR Results
Designing Data Roles
Final UXUI
Results
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
Role Flexibility
Roles Now Editable + Reusable
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and copy them to speed up setup.
To reduce friction, we kept the original 3 canned roles—but made them editable. Admins can now invite multiple users at once, assign reusable roles during setup, and complete everything in a 3-click flow.
Setting up a 6-person team used to take 20–25 minutes, requiring manual role creation for each user with no editing after saving. Now, it takes under 7 minutes—a 70% time savings. That efficiency translates directly to smoother implementations and a better customer experience.
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
Role Flexibility
Roles Now Editable + Reusable
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and copy them to speed up setup.
To reduce friction, we kept the original 3 canned roles—but made them editable. Admins can now invite multiple users at once, assign reusable roles during setup, and complete everything in a 3-click flow.
Setting up a 6-person team used to take 20–25 minutes, requiring manual role creation for each user with no editing after saving. Now, it takes under 7 minutes—a 70% time savings. That efficiency translates directly to smoother implementations and a better customer experience.
Adding Team Members
Reduced to 3 clicks
Permission Setup Time
Reduced by ~70%
Role Flexibility
Roles Now Editable + Reusable
Scalable, Flexible Permissions Built for Finance
Cube’s old permissions were rigid—teams couldn’t assign access across dimensions like region or department, and admins couldn’t even edit roles after setup. It didn’t scale.
We redesigned permissions to match how finance teams actually work. Now, admins can assign read/write access by dimension (e.g. “EMEA Forecast, View Only”), edit existing roles, and copy them to speed up setup.
To reduce friction, we kept the original 3 canned roles—but made them editable. Admins can now invite multiple users at once, assign reusable roles during setup, and complete everything in a 3-click flow.
Setting up a 6-person team used to take 20–25 minutes, requiring manual role creation for each user with no editing after saving. Now, it takes under 7 minutes—a 70% time savings. That efficiency translates directly to smoother implementations and a better customer experience.