Your profile is two things at once. Inside the CMS it is how your teammates recognize you — the avatar in the rail, the name on a comment, the person a page is assigned to. On the published site it is your byline: if you write pages, author pages and bylines draw their name, photo, title and bio from this form. You reach it from the avatar at the bottom of the left rail, under My Profile.
The profile menu
Selecting your avatar opens a small menu. Four entries matter to you.
| Item | Shown when | What it does |
|---|---|---|
| My Profile | Always | Opens your user settings at /user/<your-id> |
| Switch Organization | You belong to more than one workspace | Opens the organization picker |
| Developer Setup | You have developer access — either by role, or through the developer override | Opens a dialog holding the one-line command that installs the Leed CLI |
| Sign Out | Always | Ends the session you are using and returns you to the sign-in screen |
Switch Organization is absent for most people because most people belong to one workspace — Joining and Switching Workspaces explains when it appears. Developer Setup appears for Content Publishers and above, and for anyone an administrator has given the developer override from Billing and Developer Access; the command it hands you is picked up by Installing the Leed CLI.
If you are Leed staff you will see additional entries here for administration, impersonation and debugging. They are not part of a customer workspace and are not documented.
The three tabs
User settings has three tabs across the top.
- General — the profile form itself. Always present, on your own profile and on anyone else’s you are allowed to open.
- Security — sessions, your connected GitHub account and your API tokens. It appears only on your own profile; you cannot see anyone else’s, and no role grants that. It has a page of its own.
- Notifications — present but disabled. It is grayed out and does not respond to a click, because there are no notification settings to configure yet.
Saving changes
The page editor autosaves. This form does not.
The one exception is the profile image. Choosing a new picture saves it immediately, without waiting for Save Changes, so the avatar in the rail updates as soon as the upload finishes.
What is public and what is not
The three sections of the form are not arbitrary groupings — each one carries its own promise about where the values can end up, and the form states that promise in the helper text under each heading. Read the section heading before you decide what to type.
Profile
“Details about yourself that may be public on the website.”
| Field | What it is |
|---|---|
| Profile Image | Change opens the image picker. Anything you upload here is filed in the asset library under the User Profile Picture label automatically |
| First Name, Last Name | Your display name across the CMS, and the name on a byline |
| Title | Your job title, for author pages that show one |
| Department | Free text |
| Bio | A short description of yourself, rendered on author pages that include one |
Your photo lands in the asset library like any other image, so the formats, sizes and cropping described in Uploading Images apply to it too.
Contact Info
“This information will not be publicly available.”
| Field | What it is |
|---|---|
| Your sign-in identity. Read-only | |
| Phone | Free text |
| Country | One of US, CA, EU |
| Language | One of English, Spanish, French, German, Chinese |
Social Profiles
“Connected accounts that can be public on site or used for automatic posting.”
Enter Twitter ID, Bluesky ID and Facebook ID as bare handles — the field draws the leading @ for you, so type adalovelace, not @adalovelace. These are publishing metadata, not sign-in identities: filling one in does not let you sign in with that service, and clearing one does not disconnect anything.
The Connect LinkedIn Profile button in this section is not wired up yet. Pressing it does nothing at all — no dialog, no error, no saved value. It is listed on Known Limitations with the rest of the product’s honest gaps.
Where your profile actually appears
Bylines and author pages on the published site read from the Profile section. Which of those fields a given page actually renders is a template decision rather than a profile one, so two sites built on Leed can show different subsets of the same profile.
Two things a reader might expect to find on this form are not on it: whether you are offered to templates as an author at all, and the author slug your author page is published under. Both live on your row in Managing Team Members, because they are decisions about the site rather than about you. And being named as an author on a page is not only cosmetic — it grants access to that page, which Authors and Contributors covers in full.
Editing someone else’s profile
Their Security tab is never visible to you, however senior you are. Sessions, connected accounts and API tokens are reachable only by the person who owns them.
Nothing on this form changes anybody’s role — including your own. Roles are set on the team screen, never on a profile.
Signing out
Sign Out in the profile menu ends the session you are currently using and returns you to the sign-in screen. It ends that session and nothing else: another browser, another machine, and any terminal signed in with the Leed CLI all stay signed in until they expire or you revoke them from the Security tab.