How to Let Users Manage Their Own Profiles
Where Profile Data Lives
User profiles are split across two rows in the customers table. The main row (sorted by account ID with sort key "main") holds credentials, active apps, and account settings. The data row (sort key "data") holds personal details like first name, last name, phone number, and company. This separation keeps authentication data separate from profile information, which is cleaner for both security and data management.
When a user edits their profile through your portal, the system updates the appropriate row in the customers table. Changes take effect immediately since the database is read on every request.
Setting Up Profile Management
The Account Admin app includes a built-in settings page that lets users edit their profile fields. Add this page to your portal navigation so users can find it from the main menu. The page reads the current user's data from the customers table and presents it in an editable form.
Decide which profile fields to expose. Common editable fields include first name, last name, phone number, company name, and notification preferences. Some fields like account ID and email address are typically read-only since changing them affects authentication. You control which fields appear and which are editable through the page configuration.
Include a password change section on the settings page. The form should require the current password for verification before accepting a new one. The platform handles password hashing automatically, so the new password is stored securely without any additional code on your part.
If your portal sends email or SMS notifications, add preference toggles so users can control what they receive. These preferences can be stored as fields in the user's data row and checked by your notification logic before sending. Users appreciate control over their communication, and it reduces unsubscribe complaints.
What Users See
The profile page presents a simple form with their current information pre-filled. Users edit the fields they want to change and click save. The system validates the input, updates the database, and confirms the change. If the user tries to change their email to one that already exists, the system rejects the change with a clear error message.
For portals with role-based access, different user types can see different profile fields. An admin user might see billing information and API keys, while a regular user only sees their contact details and password.
Custom Profile Fields
You can extend profiles with custom fields specific to your business. A fitness portal might add fields for height, weight, and fitness goals. A client portal might add company size, industry, and preferred contact method. Custom fields are stored in the data row alongside the standard profile fields, so they work with the same update mechanism.
Give your portal users self-service profile management. Name, contact info, password, and custom fields.
Get Started Free