The Permissions tab is visible to Owners by default. If you don’t see it, or want to open it to Admins, contact your CSM.
How access is built
A person’s access is the combination of four things. Reading them together tells you exactly what they can do.
A person’s effective access in any area is the higher of their base role and any per-area grant. Per-area access can only raise what someone can do — it never takes access away.
Base role
Everyone has one base role that applies across the whole platform. From lowest to highest:The Permissions view lists people up to Owner. Internal and service accounts above that level aren’t shown or edited here.
Per-area admin access
Instead of making someone a full Admin, you can give them admin access in one area only — for example, someone who manages all your content but nothing else. Each area is a checkbox on the person’s detail page. Ticking it grants admin access in that area; unticking removes the grant.Named roles
Named roles switch on a specific set of capabilities. Two can be assigned here:- IT admin — manage security settings, SSO, and automated user provisioning.
- Buyer — approve learning requests and manage credits, payments, and the catalog.
Individually granted features
Some people have extra features switched on just for them. These appear on the detail page as read-only chips under Individually granted features. They’re managed by Juno support and can’t be changed from this view.Permission areas
Per-area admin access covers 10 areas. This is what each one unlocks:Nine of these areas can be granted directly on a person’s detail page. Feedback is shown for context but can’t be granted here — it follows the person’s base role.
A Content area admin sees activity for everyone in the content analytics lists under Admin → Content, not only for their own reports.
Who can assign learning
Two things decide who you can assign a unit to: your role, and whether you created or co-edit that unit.
Anyone can assign themselves learning they can see. That’s never limited.
Setups your organization can choose
The table above is the Standard setup. Juno support can switch your organization to another one:
Admins, Owners, and Content area admins assign to anyone in every setup. A Manager & Instructor assigns to anyone in every setup except Admins only. Learners assign only themselves, unless they created or co-edit the unit and your setup lets co-editors assign anyone.
To change your setup, ask Juno support and name the setup you want. The change applies to everyone in your organization.
Where these rules apply
The same rules apply everywhere you can assign or remove people:- Assign to people / groups in a unit’s Share menu. If you can’t assign, the option is hidden. If you created or co-edit the unit, Share stays when it has other options, such as Copy link.
- The Assign Learners tab when you publish a unit.
- Assign user in content management.
- Remove users in Training Analytics. You can remove only people you could assign.
- Assigning through an AI assistant.
The permissions table
Each row is one person. The table supports server-side search, filter, and sort.
Above the table, a row of summary chips shows every permission configured across your whole organization with a count of how many people hold it. Select a chip to filter the table to those people.
The “Manages” column
The Manages column summarizes who a person oversees:- Direct — people who report to them directly.
- In hierarchy — everyone further down their reporting line.
- Groups — permission-granting groups they administer.
Search, filter, and export
- Search matches on name and email.
- Filters narrow by base role, area, and named role.
- Export downloads the current filtered view. Exports are capped at 10,000 rows — if you hit the cap, narrow the filters and export again.
The person detail page
Select any row to open that person’s full breakdown.- What this person can do — a checklist of every area and named role. Areas already covered by the person’s base role show as checked and disabled, labelled From their base role (an Admin already administers every area, so there’s nothing extra to grant).
- Who they manage — the people they oversee, tagged by reason: Direct report, Reporting line, or Managed via and the group’s name. Long lists show the first 200 people, but the counts always reflect everyone.
- Individually granted features — read-only chips, shown only when the person has them.
Changing someone’s access
You need the Admin base role to change access. There are two ways to make a change.Change the base role
Pick a new base role from the dropdown. Before anything is saved, a confirmation dialog shows exactly what will change — the base role itself, any area whose effective access changes, and any named roles added or removed. Confirm to apply.Grant an area or named role
Tick or untick an area or named role in the checklist. These changes apply immediately — there’s no confirmation step.You can’t set someone above your own level or edit someone who’s above you. If a change isn’t allowed, it isn’t applied and you’ll see a message that you may not have permission to make it.
Who can see and change permissions
- See the Permissions tab — Owners by default. Your CSM can open it to People admins (the Admin base role or a People area grant).
- Change access — the Admin base role, within the limits above.