Juniper Mist Configuration Basics · Topic 1 of 4
Administrator Accounts, Roles and Authentication
Learn Mist admin accounts for the JN0-253: inviting admins, Super User to Installer roles, site access, password policy, 2FA, SAML SSO and global accounts.
- 6 min
- The account that creates an org is its Super User; others are invited on Organization > Admin > Administrators.
- An invite sets the role and Site Access: All Sites, Site Groups or Specific Sites.
- Super User manages admins and sign-in settings; Org Admin does everything else at org level.
What it is
Every person who works in the Mist portal has an account, and each account has a role in each organization it can reach. The role decides what the person can see and change, and the site access setting decides where.
The first account that creates an organization becomes its Super User, with full access. Every other administrator is invited by an existing admin, and the organization's settings control how they sign in: password rules, two-factor authentication and single sign-on (SSO).
How it works
Creating the first account and organization
- Go to the portal for your region, such as manage.mist.com for Global 01, and choose Create Account.
- Confirm the validation link Mist emails to you.
- Sign in and click Create Organization, then enter a name.
Mist creates a site named Primary Site inside the new organization. You become its Super User.
Inviting and managing administrators
Admins are managed on Organization > Admin > Administrators. This page lists every user, including limited roles such as installers.
- Click Invite Administrator.
- Enter the user's email address and contact details.
- Under Administrator Roles, select the role.
- Under Site Access, keep All Sites or choose Site Groups or Specific Sites.
- Click Invite.
The invitee receives an email, accepts it, and then gets a confirmation email with a link to create a login. One account can belong to several organizations, with a different role in each.
The administrator roles
| Role | What it can do |
|---|---|
| Super User | Full read and write access to the whole organization, including managing other admins and sign-in settings |
| Org Admin | Read and write to nearly everything, including org-level configuration, but not admin management or login and authentication settings |
| Network Admin | Site-level configuration for the sites granted; cannot claim or assign devices or configure org-level features |
| Observer | Read-only access to the allowed sites; with All Sites, also read-only Inventory |
| Helpdesk | Read-only access plus basic device actions such as reboot, upgrade and tests, basic RF management and manual packet capture, with no configuration changes |
| Installer | For a set grace period, can claim, assign and unassign devices and place APs on floor plans, through the Mist AI app or the API; cannot use the portal and cannot unclaim devices |
| Super Observer | Monitors all sites and views organization pages |
| Switch Port Operator | Views and manages the switch port settings a Super User allows |
| Reporting | Read-only access to analytics pages |
| Location | Read and write access to location features such as Live View and engagement and occupancy analytics |
| Marketing | Read-only access to the same location features |
| Mist Edge Admin | Full control limited to Mist Edges and Mist Tunnels at the sites it can reach |
A Network Admin with Selected Sites or Site Groups has no access to audit logs, inventory or support tickets. A check box, Allow read access to select org level configurations, can give it read-only access to org templates.
Only a Super User can manage other administrators and change login settings. If a question asks who can invite an admin or turn on SSO, the answer is Super User, not Org Admin.
Authentication methods
| Method | How it works | Notes |
|---|---|---|
| Local password | Email address and password on the regional portal | Governed by the org password policy |
| Two-factor authentication | A code from an authenticator app after the password | Optional for regional accounts, mandatory for global accounts |
| SSO with SAML 2.0 | The identity provider (IdP), such as Azure, ADFS, Google or Okta, authenticates the user | Password policy does not apply; the IdP enforces it |
| Global account | One sign-in that reaches orgs on every regional cloud | Requires MFA; can use Sign in with Google or Global SSO |
Password policy
The policy is set on Organization > Admin > Settings in the Password Policy section. Select Enabled, then set:
- the minimum password length
- whether special characters are required
- whether Two factor authentication is required
- a password reset period in days, with a reminder banner 14 days before expiry
Single sign-on
SSO identity providers are added in the organization settings. Any IdP that supports SAML 2.0 works.
The SAML NameID attribute is required and identifies the account; FirstName and LastName are recommended. A Role attribute maps the user to a custom role created in Mist for SSO.
Always keep at least one local Super User account when you use SSO. If the IdP fails, for example because its certificate expired, that local account is the only way back into the portal.
Global accounts
A global account is separate from your regional accounts and is linked from My Account > Link to Global Account. It needs multi-factor authentication through an authenticator app or an emailed one-time password.
Sign in with Google can then be enabled, and Global SSO ties a domain and its IdPs to the account. Orgs, data and roles stay in their regional clouds.
Common mistakes
Giving Network Admins the job of claiming devices. Network Admins cannot claim or assign devices. Use an Installer for site installs, or a Super User or Org Admin.
Expecting an Installer to use the portal. The Installer role works through the Mist AI app and the API only, and only during its grace period.
Applying the password policy to SSO users. SSO users authenticate at the IdP, so the Mist password policy does not affect them.
Treating Helpdesk as read-only. Helpdesk can reboot, upgrade and run tests, but it cannot change configuration.
What to remember for the exam
- The account that creates an org is its Super User; others are invited on Organization > Admin > Administrators.
- An invite sets the role and Site Access: All Sites, Site Groups or Specific Sites.
- Super User manages admins and sign-in settings; Org Admin does everything else at org level.
- Network Admin and Observer are site-scoped; Network Admins cannot claim devices.
- Installer: claim, assign and place APs during a grace period, via app or API, no portal, no unclaim.
- Helpdesk: read-only plus reboot, upgrade, tests and manual PCAP.
- Password policy and 2FA live on Organization > Admin > Settings.
- SSO uses SAML 2.0; NameID is required; keep a local Super User.
- Global accounts need MFA and reach orgs in every regional cloud.
Check yourself
A contractor must claim APs and place them on floor plans for two weeks without portal access. Which role fits?
Installer, which can claim and assign devices and place APs through the Mist AI app or the API for a set grace period.
Why should you keep a local Super User after enabling SAML SSO?
If the identity provider fails, for example with an expired certificate, the local Super User can still sign in and fix the settings.
Can an Org Admin invite another administrator?
No. Managing other admins and changing login or authentication settings needs the Super User role.
Topic 1 of 4 in Juniper Mist Configuration Basics
Test yourself on Juniper Mist Configuration Basics
The full Juniper JNCIA-MistAI JN0-253 question bank has 668 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.