Account Creation
Examples
Description
A component that lets people without an account in the system create their first user account. It presents an interface accessible without prior authentication, where the user provides their basic data or links their identity through other means. The system validates the information, creates the new account, and stores the credentials securely so that they can later be used to authenticate.
Mandatory capabilities
Mandatory capabilities
- Is accessible without prior authentication
- Validates the input data according to the system's rules (email format, password strength, username uniqueness)
- Stores the new user's credentials or identifiers securely in the repository
Additional capabilities
Additional capabilities
- Prior verification by email or SMS: requires the user to confirm possession of the declared contact channel before the account is activated, through a code or link sent to their email or phone
- Anti-spam captcha: includes challenges to prevent automated sign-ups by bots
- Manual administrator approval: keeps the account in a pending state until an administrator explicitly approves it
- Invitation code restriction: limits registration to those who hold a previously issued code, controlling who can join the system
Boundaries
What it is not
- Does not authenticate the user after the account is created — that belongs to Login Form
- Does not modify existing accounts — that belongs to Profile Management
- Is not the administration of accounts by authorized staff
Information flow
Input
The new user's data (email, password, name, basic profile data) or a device or biometric identifier
→
Output
A new account created in the repository, together with a confirmation or welcome notification when applicable
Variants
- Traditional registration: a form with email or username and password
- SSO registration: "Sign up with Google/Microsoft/Facebook", delegating the data to the provider
- On-device registration: linking the account to the device through fingerprint, PIN, or pattern (common in mobile apps)
Typical dependencies
- User repository where the new account is stored (Database)
- Data validator (business rules on passwords, emails, etc.)
- Notification service (Notification System to send confirmations)
- Captcha or anti-spam system (when that capability is present)
Mapping to the Digital Board
Manual UpdateAlways
Automatic UpdateNo
Data ConceptsAlways
On-Demand OutputsNo
Automatic OutputsOptional
Autonomous ProcessesNo
| Section | Relationship | Notes |
|---|---|---|
| Manual Update | Always | Registration form that the user fills in with their data. Captcha and invitation code, when those capabilities are present. |
| Automatic Update | No | — |
| Data Concepts | Always | User (the newly created account). |
| On-Demand Outputs | No | — |
| Automatic Outputs | Optional | Welcome email or SMS; prior verification code, when that capability is present. |
| Autonomous Processes | No | — |
Digital Board example
Manual Update
Registration Form
Data Concepts
User
On-Demand Outputs
—
Automatic Update
—
Autonomous Processes
—
Automatic Outputs
Welcome Email
Email Verification Code