# Usernames Feature

Focus was placed on the aspects central to increasing user privacy and security. This included creating username functionality and creating station nicknaming functionality.

<figure><img src="/files/bvTfrte74Jv0ful46pxt" alt=""><figcaption><p><mark style="color:red;"><strong>REDO</strong></mark></p></figcaption></figure>

**Feature Details:** Usernames were created to protect the privacy of users because at that time, emails were used for display names to the public. Usernames were created to by unique per user.

**Feature Flows:** The usernames feature were account for three user flows: 1. New users opening the app after the update, 2. Existing users opening the app after the update, 3. Users changing their nickname after the first open from settings. New and existing users have the same flow for opening the app after the update, with one exception for existing users. They are presented with a modal notification letting them know why they will be required to create usernames and what they will see next, since existing users will have expectations of what they will see upon opening the app and their expectations will not be confirmed. Afterwards, the user will see a screen with a profile image populated if they had previously uploaded one or a blank profile image placeholder that states that this field is optional, alongside an autopopulated username based on their email address (without *@domain.com*) **(see diagram 1)**. If they decide to change either fields, they will be directed into the photo and username flows as appropriate **(see 2–3)**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ecosphereprime.com/ecosphere/community-product/usernames-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.