Project & environment settings + access keys

Overview

As UXCam's product grew to support multiple projects and environments, the existing settings structure couldn't scale. This project redesigned how users manage project settings, environment configurations, and API access keys within a unified, intuitive interface.

Problem

Settings were scattered across different sections with inconsistent patterns:

• Users struggled to find specific settings as the product expanded
• Access key management was buried and lacked clear environment separation
• No clear hierarchy between organization, project, and environment-level settings
• The settings UI didn't scale with the growing number of configuration options

Process

I conducted a settings audit to catalog every configuration option, then worked with engineering to understand the technical hierarchy. Through card sorting exercises and information architecture analysis, I established a clear mental model for how settings should be organized.

I created detailed specs for each settings section, documenting interactions, edge cases, and access control considerations.

Solution

The redesigned settings follow a clear three-level hierarchy: organization → project → environment. Access keys are prominently placed with clear environment labels, copy-to-clipboard functionality, and rotation workflows. The sidebar navigation makes the full settings scope visible at a glance.

Outcome

The new settings architecture reduced support tickets related to configuration issues. Users could find and manage their settings independently, and the scalable structure accommodated new settings as the product continued to grow.