Bosca / Studio

Studio Personas

One app, shaped per person

Bosca spans a lot of ground. A Studio Persona decides how much of it any one person meets — so the editor, the analyst, and the operator open the same app and each find the work that's theirs.

The idea

A named set of subsystems

A Studio Persona is exactly that: a name, a short description, and the subsystems it covers, attached to a profile. Someone can carry more than one — a person who edits content and runs the analytics both gets everything each persona brings, combined into a single set.

  • A name, a description, and the subsystems it grants.
  • Attached to a profile, and switched on or off as needed.
  • Hold several, and their subsystems combine into one set.
persona
Editorenabled

Writes and publishes content, and keeps translations moving.

CMSLocalizationCalendar

Where it shows

It shapes the whole shell

A persona is the reason Studio looks the way it does when you open it. The sidebar, the switcher, the search results, and the hub you start from all follow from the set of subsystems you hold.

  • Navigation offers the subsystems your personas cover.
  • Search and quick actions reach the same set.
  • Administrators see the whole platform.
effect
The sidebarOnly the subsystems a persona grants are there to navigate.
The switcherThe categorized modal lists the same set, and nothing else.
Search & actionsDestinations and quick actions follow the subsystems you hold.
The home hubThe launcher grid lists the subsystems your personas cover.

Assigning them

Defined once, attached where you work

Personas are defined in System security, alongside the rest of the platform's access settings. Attaching one happens where you already manage people — on a profile's Security tab in Audience — so giving someone the analytics view is part of the same visit as the rest of their setup.

Keep exploring

More on Studio