Asana — Account entry

Forms & OnboardingSee it liveapp.asana.com

A centered account-entry panel offers Google and Microsoft before a clearly separated email path.

Asana — Account entry — captured interface — Viewport capture · opening screen

Source capture · 2026-09-05Open full image ↗

Forms & onboarding

Why this pattern works

Work software that supports both company identity providers and email entry.

Design notes

Surface: Asana public sign-in screen reached from its signup route.
Navigation: Minimal entry screen with corporate and support links in the footer.
Layout: Narrow centered form with provider buttons, divider, email field, and Continue.
Density: Low and task-focused.
Color: White, dark text, pale gray boundaries, small brand accents.
Type: Simple sans heading with clear provider and field labels.
Pattern: Present provider-based access and email as distinct, understandable routes.
States: Initial sign-in state, not an authenticated dashboard or completed signup.
Don't: Do not imply that clicking Continue immediately creates an account when the next step may identify an existing one.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Asana — Account entry
Source: https://app.asana.com/-/login
Swipefile reference: https://swipefile.design/ref/saas-ui-asana-create-account/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Asana public sign-in screen reached from its signup route.
- nav: Minimal entry screen with corporate and support links in the footer.
- layout: Narrow centered form with provider buttons, divider, email field, and Continue.
- density: Low and task-focused.
- color: White, dark text, pale gray boundaries, small brand accents.
- typography: Simple sans heading with clear provider and field labels.
- pattern: Present provider-based access and email as distinct, understandable routes.
- states: Initial sign-in state, not an authenticated dashboard or completed signup.
- dont: Do not imply that clicking Continue immediately creates an account when the next step may identify an existing one.

Useful for: Work software that supports both company identity providers and email entry.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Work software that supports both company identity providers and email entry.

Asana — Account entry

Make it your own

Keep exploring