# Profiles

Set your name, contact details and headshot once, and every tool built to use them fills them in for you: an email signature, a badge, a speaker card. That small record is your **profile**, and it lives on your device.

Your profile also holds what you build up while you work: saved sessions, uploaded images and your local activity tally. You manage it under **Settings → Preferences**; tools only ever read the fields they were built to pre-fill. Standalone use needs no account, and optional Sync, sharing and organisation services each have their own data flows, described below.

## What's in a profile

| Part | What it is |
|---|---|
| **Name** | First and last name. |
| **Contact** | Email and phone. |
| **Location** | City and country. |
| **Headshot** | An optional photo, cropped to a square and kept as a local image, for tools such as email signatures, quote cards and org charts. |
| **Use my details to create** | One opt-in switch (it reads **Using my details** once on). It decides whether your details travel as the author credit in exported files and on Batch runs. It does not affect pre-fill; see [How tools use your profile](#how-tools-use-your-profile). |
| **Preferences** | Your theme, your accessibility settings and which parts of the app you turned on in **Feature flags**. |
| **Your work** | Saved sessions with their thumbnails, organised in [Projects](/info/create/find-your-work.html), your uploaded images and your local activity stats. |

None of it is required. A blank profile works; fill in only what saves you typing.

![Settings on the Preferences tab: the settings rail, and Your details with the Use my details to create switch and the name, contact and location fields](/t/url-shot?url=%2F%23%2Fsettings%3Ffocus%3Ddetails-section&width=1440&height=900&dpi=192&waitMs=1600&format=svg&walker=1&localize=1&dark=1&filename=profile-details)

[Settings](/info/create/dashboard.html) maps everything else under Preferences, from appearance and emoji to storage and offline downloads.

## You, a team or a role

The word "profile" suggests one fixed person. In Lolly it is closer to a creating context: who you are while you make this thing. It can take three shapes, and Lolly handles each the same way.

::: cols
## As yourself

The default. Your name, your email, your headshot. Set it once and your signature, badge and conference lockup fill themselves in.

## As a team

A team's shared name, a group inbox such as `events@…`, a department and the team's mark. One person sets it up and exports it, and everyone else loads the same profile, so the team's files carry consistent details. A shared kiosk or a demo laptop can run one team profile.

## As a role

An event manager three days a year wants the event inbox and the event sub-brand on badges and signage, then their usual identity back. Keep that role as a saved profile file, load it for the event and set it aside afterwards.
:::

![The headshot control, empty until you upload a photo that then stays on this device](/t/url-shot?url=%2F%23%2Fsettings%3Ffocus%3Ddetails-section&width=1440&height=900&dpi=192&waitMs=1600&format=svg&cropSelector=.profile-side&walker=1&dark=1&filename=pd-profile-headshot&css=.profile-details-main%7Bdisplay%3Anone%7D)

**Profiles at an organisation using Lolly Work**

When you sign in to an [organisation's Lolly](/info/start/organisation.html), Lolly Work can supply verified profile fields from its identity provider and fix fields or preferences under organisation policy. A managed field is labelled in the app.

That sign-in also controls access to shared projects and assets. A team profile file is still a local file: it does not grant organisation membership or replace a work account. **Use my details to create** controls the credit in your exports, not the organisation's sign-in or audit records. See [Privacy](/info/trust/privacy.html#organisation-services-with-lolly-work).

## Keep several, use one

An install has one active profile at a time, and there is no in-app switcher. Instead, each profile is a portable file, the same backup file you would use to move to a new device. To step into another context:

::: timeline
- <!--i:download--> **Export my data** under **Settings → Storage → Move to another device** saves the current profile as one `.zip`.
- <!--i:trash--> **Clear all my data** empties this install.
- <!--i:upload--> **Import data…** loads the profile file for the context you are stepping into.
:::

Importing without clearing first **merges** instead. Imported sessions and images are added; where both copies exist, the one saved more recently is kept. Folders, favourites and templates are added beside yours, and your own details stay, apart from empty fields, which take the file's values. That suits pulling one team's sessions into your own setup, but not a clean break between roles.

For two contexts at once, use a separate browser profile, a separate user account or a second installed copy of the web app: each carries its own independent Lolly profile.

![The two buttons that move a whole install: Export my data writes one zip, Import data reads it back](/t/url-shot?url=%2F%23%2Fsettings%3Ffocus%3Dstorage-section&width=1440&height=1800&dpi=192&waitMs=2400&css=.store-move%3Ediv%3Anth-of-type%282%29%2C.store-move%3Ep%3Alast-of-type%7Bdisplay%3Anone%7D&waitSelector=%5Bdata-store-group%3Dmove%5D&drive=click%3A%5Bdata-store-group%3Dmove%5D%3Esummary&walker=1&format=svg&cropSelector=%5Bdata-store-group%3Dmove%5D&dark=1&filename=pd-transfer-controls)

> Keep one file per context and name each for what it is, such as `LollyTools-events-2026.zip` and `LollyTools-me.zip`. The file is the profile.

[Move your work to another device](/info/create/find-your-work.html#move-your-work-to-another-device) covers what the file holds, what stays behind and the other ways to move, including Sync.

## How tools use your profile

**Pre-fill.** A tool author marks an input as drawing from your profile (`bindToProfile: "firstname"`, `"email"`, `"headshot"` and so on). When the tool opens, that input fills from your profile, and you can override it for one session without changing the profile, unless an organisation policy locks the input. Pre-fill is a local convenience and happens whether or not **Use my details** is on.

**Credit.** When you export, your details can travel as the author credit in the file's metadata (PNG, PDF, SVG and more), so a finished file can say who made the work. **Use my details to create** governs this, and the author on Batch runs. With it off, the export still says it was made with Lolly, and carries no personal author or contact line.

Tool authors: see [`bindToProfile`](/info/build/tool-inputs.html#bindtoprofile) and [`host.profile`](/info/build/host-api.html#host-profile).

![The single Use my details to create switch, marked opt-in and off until you turn it on](/t/url-shot?url=%2F%23%2Fsettings%3Ffocus%3Duse-details&width=1440&height=900&dpi=192&waitMs=1600&format=svg&cropSelector=.profile-check&walker=1&dark=1&filename=pd-use-my-details)

## Profile, design system and capabilities

Three things sit near each other in Settings and are easy to confuse:

- <!--i:people--> **Profile** - you, your team or the role you are in: name, contact, headshot and saved work. Personal, kept on the device and portable as a file.
- <!--i:palette--> **Design system** - the brand: colours, fonts and settings every tool renders with. Shared and consistent rather than personal; see [Design System Setup](/info/create/brand-studio.html).
- <!--i:sliders--> **Capabilities** - what the app can do: the features and tools available to you.

A profile changes who a file is from; the design system changes how the file looks; capabilities are what you can make.

The word has three other meanings in Lolly. A **content profile** is a build setting that chooses which tools and catalogue a deployment ships; the [Glossary](/info/start/glossary.html) defines the term. The `profile` link parameter picks a colour profile for an export, such as a CMYK press condition; see [Reserved URL parameters](/info/build/url-parameters.html#print). A **verified identity** is the optional signing certificate that ties your email to your signed exports, separate from these details, though **Use my details to create** governs whether either is embedded; see [Content Credentials](/info/trust/content-credentials-identity.html).

![The Verified identity card, phone-width: the certificate lifetime picker and the enrolment step beneath it - the identity profile, separate from your personal details](/t/url-shot?url=%2F%23%2Fsettings%3Ffocus%3Didentity-section&width=430&height=1600&dpi=192&waitMs=2400&css=.welcome-dialog%2C.personalize-nudge%7Bdisplay%3Anone%7D&format=svg&walker=1&cropSelector=%23identity-section&dark=1&filename=pv-identity-enrol)

## Privacy

Your personal profile is stored locally. Your details can travel in a backup or Sync copy, in content you share or export and during optional Content Credentials enrolment. On a Lolly Work instance, sign-in, shared work, telemetry policy and audit records are separate from this local profile. **Settings → Preferences → Clear all my data** clears this device; it does not erase copies held by your storage provider or organisation. See the [Privacy Policy](/info/trust/privacy.html).

---

Code ([MPL 2.0](https://www.mozilla.org/en-US/MPL/2.0/)) · Content ([CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/)) · [lolly.tools](https://lolly.tools)