Admin screen Layout
- Header:
- Logo/Organization Name: Clearly displayed at the top.
- Admin Info & Notifications: A small profile icon or name with a logout button and notification
screen clearly gives focus on the admin screen.
- Global Search: Optionally, a simple search bar to quickly look up users or functions.
- Sidebar Navigation (Left):
A vertical menu with clearly labeled items such as:
- Dashboard (Home)
- Issue Identity
- Revoke Identity
- Send notifications & app messages
- User Management
- Basic analytics
- Settings
(For MVP, menu item that includes basic role management and audit logs.)
- Main Content Area:
The largest area, where the selected module’s content is displayed.
Dashboard Overview Screen (Default Landing View)
1. Metrics Cards:
At the top of the main area, display a row of summary cards. For example:
- Total Identities:
- Display the total number of active identities.
- Use a bold number with an icon.
- Pending Requests:
- Show how many identity issuance requests are awaiting admin action (e.g., “12”).
- Revoked Identities:
- Indicate the number of credentials that have been revoked (e.g., “50”).
Visual Tip: Use card components with a simple background, an icon, and a number. Cards
should be clickable if you want to allow drill-down (e.g., click “Pending Requests” to see a list).
2. Recent Activity Feed:
Below the metrics, provide a scrollable panel or a list view that shows the most recent actions:
- Examples:
- “Issued Identity to Alice on 2023-10-01.”
- “Revoked Identity for Bob on 2023-09-30.”
- Keep the list short (e.g., 5–10 items) with an option to view more in a separate “Activity Log”
page.
3. Quick Action Buttons:
Prominently display buttons for the most common tasks:
- [Issue Identity]
- [Revoke Identity]
These buttons should be large and visually distinct, inviting immediate action.
4. Optional Analytics (Minimal):
For an MVP, a simple line or bar chart can be placed at the bottom or on a side panel that
shows trends over time (e.g., identities issued per month). This can be very basic—if it
complicates development, you might choose to defer detailed analytics to later releases.
Additional Screens (Simplified for MVP)
1. Identity Issuance Screen:
- Form:
A simple form with fields like:
- User’s DID (or a way to search for a pre-registered user)
- Credential Type (dropdown: “Employee,” “Member,” etc.)
- Optional expiration date and custom attributes
Similar to user onboarding screen
Also if a user sends a request to admin from onboarding screen admin/issuer will get all the
details and admin can set expiry date and proceed it accordingly.
- Preview & Confirm:
A preview panel that shows how the credential will appear, then a button to “Issue Identity.”
After this admin or issuer is promoted to enter the password/pin to issue it.
And identity is issued
- Bulk Option:
For MVP, might offer a CSV upload option, but it could also be it can be opted out if it
complicates things.
2. Identity Revocation Screen:
- Search/Filter:
A simple search box to find a user by DID or name.
- Selection & Revocation:
Once a user/credential is selected, display a minimal revocation dialog with a field for
“Revocation Reason” and a confirm button.
Atleast an admin is required along with issuer to revoke an identity no single issuer can revoke
the identity.
3. User Management Screen:
- User List:
Display users in a table with columns such as DID, Name, Credential Type, Issuance Date,
and Status (Active/Revoked).
- Detail View:
Allow admins to click on a user to see detailed history (issuance events, revocations).
- Filtering/Sorting:
Keep this basic for now simple text search should suffice.
4. Security & Settings (Basic):
- Role Management:
A very simple screen to view current admin roles and add/remove admins.
- Audit Logs:
A read-only view of recent admin actions for accountability.
- Integration/Key Management:
For MVP, these can be displayed as read-only or simple settings with minimal configuration.
Design & Usability Considerations
Clean, Minimalistic UI:
Focus on clear typography, ample whitespace, and a consistent color scheme. Icons should be
used sparingly to reinforce actions (e.g., a key icon for security, a plus sign for “Issue Identity”).
- Responsive Design:
Although admins typically use desktops, ensure the layout adapts well to different screen
sizes.
- Guidance and Tooltips
For complex terms (e.g., DID, multisig), include tooltips or help links. Keep documentation
accessible.
- Performance:
Since this is an MVP, the dashboard should load quickly. Optimize by loading only key data on
the main screen and allowing deeper details in separate views.
Summary
For an MVP admin dashboard, aim for:
- A header and left sidebar for navigation,
- A main dashboard view with key metrics (Total Identities, Pending Requests, Revoked
Identities),
- A recent activity feed for transparency,
- Quick action buttons for issuance and revocation,
- Separate screens for Identity Issuance, Revocation, and User Management that keep forms
simple and focus on the most critical functions.
What data can be seen by the admin panel?
The goal is to show enough information to manage and audit identities effectively while keeping
the interface clean and uncluttered for an MVP, also focusing on minimal data collection.
Minimal Details to Display by Default
For each DID entry in a list or table, consider displaying:
1. Unique DID Identifier:
○ The DID address (or a truncated version with an option to view full details).
2. Associated User Information:
○ Name: The user’s full name (or a display name)
○ Email Address/phone no: (if available) to help quickly identify the user
(optional if this is too much privacy intrusive)
3. Credential Type / Role:
○ For example, “issuer,” “Member,” or “Admin”, this helps in quick filtering.
4. Issuance Date:
○ The date the DID was issued. This is useful for tracking the life cycle.
5. Status:
○ A clear indicator (e.g., Active, Pending, Revoked) that shows the current
state of the identity.
Additional (Optional) Details via Expandable/Detail View
To avoid cluttering the User management dashboard, you can provide a “View Details” or
expandable panel/modal for each DID. In this expanded view, include:
1. Full DID Information:
○ The complete DID string and any associated metadata.
2. Expiration Date:
○ display when the DID expires.
3. Audit Trail / History:
○ A log of major events such as:
■ Issuance (with the issuing admin’s identifier)
■ Any updates or modifications
■ Revocation events (with reasons and timestamps)
4. Custom Attributes / Metadata:
○ Any additional data defined in the credential template (e.g., department,
role specifics, custom fields).
5. Associated Template Information:
○ Which credential template was used, if applicable.
Example Layout
Imagine a table-like view with columns for each minimal detail:
---------------------------------------------------------
| DID (truncated) | Name | Credential |Issued Date | Status | [Details] |
---------------------------------------------------------
| did:ex...1234 | Alice Wong | Issuer | 2023-10-01 | Active | [View] |
| did:ex...5678 | Bob Smith | Member | 2023-09-15 | Revoked | [View] |
---------------------------------------------------------
Clicking the [View] button or an expandable arrow reveals additional details as
described.
