Organization settings
Edit your organization's name and description; the description doubles as organization-wide business context for Neuralift's generated outputs.
The About tab in Settings holds your organization’s name and description. The description doubles as organization-wide business context that keeps Neuralift’s generated outputs (narratives, personas, and recommended actions) relevant to your business, so a specific, accurate description improves their quality. This page shows you how to edit both fields and how to write a description that earns its keep.
Before you begin
- Anyone in the organization can view the About tab.
- Editing requires the admin role; see Roles & permissions.
Edit the name
- In the organization sidebar, open Settings. The About tab is shown first.
- Under Name, click the pencil (Edit) button.
- Type the new name and click Save (or Cancel to discard).
The updated name appears immediately in the About tab.
Edit the description
- Go to Settings → About.
- Under Description, click the pencil (Edit) button.
- Write or revise the text and click Save.
The field’s own hint says it best: “Provide context about this organization to guide AI features.”
Write a description that earns its keep
The description is organization-wide business context. When Neuralift generates plain-language output (segment narratives, personas, and recommended actions), a concrete description grounds that writing in your reality instead of generic marketing language.
A good description covers, in two or three sentences:
- What you sell and to whom: your products or services and your typical customer.
- How you reach customers: the channels that matter to you.
- What you’re trying to achieve: the outcomes your team cares about.
For example, the app’s own placeholder points in the right direction: “E-commerce clothing brand focused on sustainable fashion.” Expanding that with your customer base and goals gives Neuralift even more to work with.
Tip. The description is organization-wide context. Goals, KPIs, and context specific to one project belong in that use case’s definition instead; see Defining the use case.
Next steps
- Add project-level context: Defining the use case
- Manage your team: Members & roles
- Connect your data: Data connections