← Previous6 / 28Next →

Popwork Users & Roles

PopworkThe app for managers and their teams

Design with AI

Create a new design inspired by Popwork Users & Roles, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 995 words

# Design from Reference: Popwork Users & Roles

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Popwork
- **Category:** Settings
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/c1b7a7174985e3713370-1600.webp)

Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.

## Visual Design Context

### Overall aesthetic

- **Style:** Warm-toned user-management settings page with a pale peach sidebar and compact two-row table.
- **Character:** Near-white main canvas, dark olive-gray copy, navy creation action, and soft rounded selection/status chips.
- **Density:** Functional controls concentrate near the top, leaving a large blank lower area.

### Page composition

- **Capture and scale:** 2880 × 1644 image px. CSS estimates assume a 2× capture, approximately 1440 × 822 CSS px; scale is unverified.
- **Sidebar:** Approximately 268px wide, brand top, settings-back label, six destinations, and separate red logout link.
- **Main area:** Starts near x=314 CSS px with title, subtitle, thin rule, and Create user action.
- **Filters:** Search field and active-user selector share one row in equal-width halves.
- **Table:** Broad rounded panel with checkbox, user, manager, role, admin, and overflow-action positions.
- **Rows:** Two visible users with colored initial avatars, name/email pair, manager relation, and role/admin badges.
- **Support:** Navy chat launcher at lower-right.

### Information hierarchy

- **Page title:** Users & roles identifies the management area.
- **Action:** Navy Create user is the strongest filled control.
- **Filtering:** Search and active-user selector precede the table.
- **Identity:** User name is stronger than the smaller gray email line.
- **Permissions:** Role/Admin columns use small neutral chips and information icons in headers.
- **Selection:** Sidebar destination has a peach highlight; row checkboxes are empty.

### Typography

- **Family:** Neutral proportional sans serif; exact identity is unverified.
- **Page title:** Approximately 18px semibold.
- **Subtitle / navigation:** Approximately 14px.
- **Table headings:** Approximately 14px semibold.
- **User names / values:** Approximately 14px regular; emails and chips around 12px.
- **Precision:** CSS sizes and weights are visual estimates.

### Colors & surfaces

- **Main canvas:** Sampled #FEFCFA.
- **Sidebar / table header:** Sampled #FAF0E6.
- **Table rows:** Sampled #FFFFFF.
- **Sidebar selection:** Sampled #F9D9BA.
- **Primary navy:** Sampled #00006B.
- **Secondary warm fill:** Sampled #F7E4D5.
- **Text:** Sampled #373525.
- **Neutral chips / boundaries:** Sampled #E1E1DF and #E0DEDB.
- **Avatar accents:** Pink and pale green circles distinguish the two users.

### Components

- **Create action:** Compact navy rectangle about 132 × 32px, white plus/label, 5px radius, and small shadow.
- **Search / filter:** Approximately 532 × 44px each with thin neutral border and 6px radius.
- **Table shell:** Warm thin outline, around 12px radius, peach header, and white rows.
- **Rows:** Approximately 68px high with fine peach separators.
- **Avatars:** About 44px rounded squares containing initials.
- **Status chips:** Small pale-gray rounded rectangles for manager/member/admin labels.
- **Overflow:** Small white outlined rounded square with three dots at row-right.
- **State limits:** No role menu, create-user dialog, checkbox selection, or permission change is visible.

### Visual rhythm

- **Alignment:** Title, action, filter row, and table share one left edge.
- **Table lanes:** Consistent identity, manager, role, and admin columns support horizontal scanning.
- **Sidebar rhythm:** Compact rows separated into navigation and logout groups.
- **Whitespace:** Short table and large blank canvas keep the management task uncluttered.

### Responsive

- **Observed state:** Desktop only; mobile behavior is unverified.
- **Navigation recommendation:** Collapse the sidebar.
- **Filters recommendation:** Stack search and status selector.
- **Table recommendation:** Use controlled horizontal scrolling or labeled row summaries without losing role/admin relationships.
- **Accessibility recommendation:** Label checkboxes, overflow controls, and information icons.

### Adaptation guidance

- **Preserve:** Warm neutral shell, clear user identity hierarchy, compact permission chips, and strong navy creation action.
- **Starting geometry:** Approximately 268px sidebar, 44px filters, 68px table rows, and 12px outer radius under the unverified 2× assumption.
- **Privacy:** Use approved example users rather than copying screenshot identities.
- **State modeling:** Define actual roles and permissions from product requirements.
- **Implementation recommendation:** Provide accessible table/filter controls and explicit feedback for edits; no user change was performed.

## Content

**Instructions:**

Generate realistic example content that fits the selected design reference.

Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.

If a product or business description is provided, use it to guide the content.

Otherwise, invent a plausible fictional SaaS product appropriate for the reference.

Keep the content concise, coherent, and visually balanced.

Do not present fictional statistics, customer names, or testimonials as verified facts.

## Design Direction

**Instructions:**

Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.

Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.

Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.

Introduce original design decisions where they improve usability, composition, or brand consistency.

The result should clearly reflect the reference's visual language without looking like a direct reproduction.

Follow the visual identity of the reference design.

Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.

Do not introduce an unrelated visual identity.

## Output

**Instructions:**

Generate a high-fidelity visual mockup of the requested interface.

Present the design as a polished, realistic website or product UI screenshot.

Prioritize visual composition, typography, spacing, colors, alignment, and component details.

Use the available image-generation or visual-design capabilities.

Do not replace the mockup with source code, a written design specification, or a textual description.

If direct visual generation is unavailable, clearly explain the limitation.

## Constraints

- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance.

Reference imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.