Account and user mangement
Ogury's platform served traders managing ad campaigns for different organizational levels. The existing permission system only supported read and edit roles—too coarse-grained for real trading workflows.
Traders needed granular control based on what level they operated at: some managed entire advertiser accounts, others managed specific desks or campaigns. The binary read/edit system created friction—either traders had full edit access (security risk) or read-only access (too limiting). No structure for different trading roles and responsibilities.
Company
Ogury
Team
1 product designer, 1 PM, 3 devellopers
Timeframe
6 month
Accounts list & Account settings drawer
Inside of an account
Drawer : Add new advertiser
Desks list
Drawer : Add new desk
Users : People & Groups page
Drawer : Add user
Drawer : Add group
Research & Approach
Interviewed internal Ogury account managers (traders): to understand workflows and organizational structure.
Benchmarked how similar platforms (Google Ads, Facebook Business Manager, etc.) structured permission systems for traders and account managers—learning from industry standards rather than inventing.
Mapped specific trader types and what they needed: platform admins, account-level traders, desk-level traders, and viewers with read-only access across campaigns.
Worked with PM to define the role structure: built permission matrices to clarify scope and responsibilities.
Solution
Role Hierarchy:
Defined five distinct roles aligned to trader responsibilities:
Admin Ogury (platform-level control)
Admin Account (manage campaigns across advertiser accounts)
Trader Account (manage specific advertiser accounts)
Trader Desk (manage desk-level campaigns)
Reader (read-only access to all campaigns)
Permission Mapping: each role had explicit permissions defining what campaign actions traders could perform. Documented which traders could create, edit, or delete campaigns at their level. Ensured consistency and prevented gaps.
UI Implementation: designed permission assignment flows for account admins. Role descriptions clarified trader responsibilities at each level. Permission UI reflected available campaign actions per role.
Outcomes
Traders could manage campaigns at their assigned level (account or desk) without blanket platform access or read-only restrictions
Granular permissions replaced binary read/edit system, enabling teams to grow without security or usability compromises
Traders operated independently within their scope; platform and account admins maintained oversight