Account settings
Understand the two account fields on this page, their scope, validation, and navigation impact.
What you see on Account settings
Account settings contains one form with Account name, URL slug, a preview of the account-scoped URL, validation messages when a value is invalid, and Save changes. These fields belong to the account workspace rather than one project. The account owns membership and projects; projects retain their own Profile, Brands, Markets, Topics, Tags, evidence, and reports.
The page contains no performance statistics. Neither the name nor slug changes Visibility, prompts, answers, products, sources, report files, usage, or audit scores. Save success means the account record was updated; it does not mean any monitoring or recalculation ran.
Account name and URL slug
| Field | What users see | What changes |
|---|---|---|
| Account name | The workspace label in the sidebar and account context. | Updates the human-readable workspace identity. |
| URL slug | The account segment used in account-scoped application paths. | Changes the path members use to open the account and its projects. |
Plan a slug change carefully
Changing the slug changes the canonical in-app path for the account. Existing browser bookmarks, copied project links, internal operating notes, and customer instructions may still contain the former path. Coordinate the change with account members and update governed links after saving.
A slug should be stable, recognizable, and safe for a URL. If validation rejects it, keep the form values visible, read the error summary, and choose a valid unique alternative. Do not repeatedly create new projects or accounts to work around a slug validation error.
Maintain the workspace identity safely
Use Account settings only for workspace identity. Use Members for roles and access, Projects for the account's measurement work, and a project's Profile for brand-study configuration. This separation prevents a workspace rename from being treated as a measurement change.
Before changing a customer-facing account name, confirm the approved organization name and who needs to know. Before changing a slug, capture important current links and plan their replacement. After saving, open the account from the sidebar and verify the new path reaches the expected projects.
- Keep the name concise enough to remain readable in navigation.
- Avoid frequent slug changes because links are operational dependencies.
- Never place secrets, personal credentials, or campaign parameters in the slug.
- Record who approved a material workspace rename and when it took effect.
- Confirm member access separately; changing the account identity does not change roles.