Profile Workspace Title, Body, and Bio Fallbacks
How the app chooses a first title and body for a profile workspace when a user has partial or missing profile details, and how professional title, about text, bio, and email fallback rules affect that first draft.
Profile Workspace Title, Body, and Bio Fallbacks
Where you see this in the app
This page documents the first title and body a profile workspace can receive when the app bootstraps it for a user.
Users usually notice this when a newly created profile workspace already has a sensible title or starter body before they manually edit anything.
How the title fallback works
The app builds a profile-workspace title from the best available identity information instead of requiring every field to be complete first.
The title always tries to feel professional and readable, even when the profile is only partially filled in.
In practice, the title uses:
- the best available display name,
- the professional title if one exists,
- a generic professional fallback when a professional title is missing.
Display name and professional title priority
The display-name side of the title follows a fallback chain.
| Source | When it is used |
|---|---|
| Profile display name | Preferred when present |
| Account name | Used if display name is missing |
| Email prefix | Last readable identity fallback before a generic label |
The professional-label side behaves similarly:
| Professional label | What the title becomes |
|---|---|
| Professional title exists | {display name} - {professional title} AI Workspace |
| Professional title missing | {display name} - Professional AI Workspace |
This means the app prefers a polished title without forcing the user to finish every profile field first.
About, bio, and starter body fallback
The first body follows a similar fallback rule.
| Body source | When it is used |
|---|---|
Profile About text | Preferred when available |
| Account bio | Used when profile About is empty |
| Starter markdown body | Used when neither profile About nor bio is available |
That starter body is intentionally generic. It explains that this is a professional profile workspace and suggests practical starter files such as:
profile.mdservices.mdpricing.mdAGENTS.md
From an end-user perspective, these are starter hints, not a locked final presentation.
What users should update after bootstrap
Bootstrap fallbacks are there to avoid an empty first impression.
Users should still treat them as draft defaults and update:
- display name,
- professional title,
- about or bio text,
- any starter body content that is too generic for their real offering.
The goal is to make first-run provisioning usable immediately without pretending the fallback text is the finished public profile.
Related docs
Related docs
See it in action
Previous
Profile Workspace Default Template and First-Run Content
How a newly provisioned profile workspace gets its default runtime shape, what starter content users may inherit on first run, and how that differs from later manual template changes.
Next
Create Posts and Manage Visibility
How posts work, what the main fields mean, and how replies, mentions, audience tags, and sharing affect the buyer or viewer experience.