Views (personas)
A view (persona lens) tailors Neens to how you work: it changes which nav items are featured, which are tucked away, your landing page, and your default time range. It never changes what you’re allowed to do — a view is a presentation default, and permissions come only from roles and your plan.
At a glance
| Where | Topbar View switcher; first-login picker; authoring under Settings → Views |
| Key API routes | GET /personas, PUT /auth/persona, POST/PATCH/DELETE /personas (authoring), POST /members/bulk-persona |
| Switching views | Free for every user, every role, every plan |
| Authoring custom views | Admins, on plans with the custom_personas feature (Silver and up) |
| Permission impact | None — hidden nav items stay reachable by URL, search, and in-app links |
A view is never a permission. Items a view hides are only hidden from the nav rail — every route stays reachable by direct URL, global search, and in-app links. Deleting the whole view layer would change nothing about security.
The built-in views
Neens ships nine platform views. Each has a home page, a default time range, and a featured/hidden nav split (everything else collapses under “All features”):
| View | Focus | Lands on |
|---|---|---|
| Executive | Fleet health at a glance — top issues and regressions | Executive digest dashboard (30-day window) |
| Developer | The full build surface — traces, judges, enrichments, eval gates | Agent home (7-day window) |
| Product manager | Quality trends, judge–human alignment, annotation throughput | PM quality dashboard (30-day window) |
| Business stakeholder | Plain-language health for the orgs you care about | Org scorecard dashboard (7-day window) |
| Domain expert | The review station — queue, disagreements, golden datasets | Review queue (7-day window) |
| Compliance & legal | Eval-gate status, issues by severity, the audit trail | Compliance overview (30-day window) |
| Finance | Spend and token usage by model, agent, and org | Cost explorer dashboard (30-day window) |
| Admin | Run the workspace — members, connections, onboarding, audit | Getting started (7-day window) |
| Full workspace | Everything featured, nothing hidden — the complete UI as one view | Overview |
A user who has never picked or been assigned a view gets a role-based default: admins get Admin, members get Developer, viewers get Business stakeholder.
Switch your view
- Topbar — the View switcher (next to the language switcher) lists every view available in your workspace; pick one and the nav re-renders immediately.
- API —
PUT /auth/personawith apersonaKey.
An explicit pick is recorded as your choice: an admin-assigned default will never silently override it afterward.
First-login picker
The first time you sign in, Neens shows a one-time picker. It pre-selects your admin’s recommendation (if one was set at invite time) or your role’s suggested view. Pick one, or skip — skipping keeps the current default and the picker never blocks you again.
View home dashboards
Several views land on a dashboard home: choosing the view auto-pins its platform dashboards (e.g. the Executive digest, the Finance cost explorer) to your favorites, and its home page resolves to the first of them. Platform dashboards render on every plan but are immutable — clone one to customize it. See Dashboards.
Assign views to your team
Admins set a member’s default view at invite time, from the member’s row, or in bulk from
the Members page (POST /members/bulk-persona) — see
Members & roles. Assigning an
existing view is free on every plan; only authoring views is gated. Members who explicitly
chose their own view are never overridden.
Author custom views
Admins on plans with the custom_personas feature (Silver and up) can tailor views under
Settings → Views:
Create a view
Name it, write a short description and up to four focus areas, pick a home route and default
time range, choose the featured and hidden nav items, and optionally attach dashboards (the
first becomes the view’s home). POST /personas.
Or customize a platform view
Editing a built-in view freezes it: it becomes a custom view owned by your workspace and
stops receiving platform upgrades. Untouched platform views keep improving automatically with
each release. PATCH /personas/{key}.
Delete when done
Deleting a customized platform view resets it to the shipped default. Deleting a
purely custom view also clears it from any member who had it as their default — they fall
back to their role-based view, so nobody is stranded. DELETE /personas/{key}.
The Full workspace view is the permanent escape hatch — it can be neither customized nor deleted, so every user can always get the complete UI.
How it works
- Views are stored per workspace. Platform views are re-synced from the product catalogue on
upgrade unless you’ve customized them (customizing sets
customprovenance, which freezes the row). - Your current view and how it was set (your own pick, an admin default, or role-derived) are stored on your user profile; the app resolves the effective view at sign-in and after every switch.
- View authoring is double-gated: the admin role and the
custom_personasplan feature. Switching and assigning are gated by neither. - Authoring events (
persona.create,persona.update,persona.delete) are recorded to the audit log.
Related
- Members & roles — assigning default views to members.
- Account settings — your own view, language, and digest email.
- Dashboards — the persona home dashboards and cloning.