🎨 [Design] : MVE3: Design superadmin access panel

[mike-mcnulty]

Summary

Admin access panel

Description

As an admin, I need a way to access the treasury space, so that I can setup and configure campaigns.

In the future, we will have on-chain admin registration like other user types. Until then, internal users will be the only admins, and will use secret API key(s) to access admin functions, in a way that functions similar to the overall RBAC / permissionless auth for the platform. Admin will need a page they can easily access where they can enter this key and access the treasury space, but this page should not be viewable / discoverable by end users.

AC:

• Build hidden page and recommend entry point
• Build component to input admin key
• Design flow from admin landing as guest in discovery space to accessing treasury space
• Consider splitting technical vs nontechnical admin access (ie configure vs detail)
• Validate approach with architects
• Validate approach with admin team

Related tasks (to be created):

• Understand admin API key requirements
• Generate API key(s) for internal admins
• Integrate admin API key(s) with RBAC / permissionless auth

[b-farrington]

Updated the prior draft design to incorporate key visibility toggle in the input field and clarified intended behaviour around key validation, including indication of loading/processing state after user clicks 'save' (Figma). Detailed component placement (in a neutral / empty page) and a basic user flow. Ready for review.

Also: suggesting use of simplified snackbars as opposed to the currently implemented ones that are functional more similar to a banner with multiple possible user actions. Could discuss, but have included alternative designs using both styles.

[mike-mcnulty]

@nielskijf @b-farrington anything outstanding here or design ticket can be closed?