Observer level access - Can no longer 'see' DHCP settings/options on Switch managed VLANs

NeilB83
Conversationalist

Observer level access - Can no longer 'see' DHCP settings/options on Switch managed VLANs

Probably can't change this but has anyone else had issues with Observer level access and the new dashboard changes? Previously you could see the DHCP settings per VLAN (DNS, options, lease time, reserved IPs etc.) on each VLAN on switches but now you can't drill down into each VLAN under Switching > Routing and DHCP.

 

I know this is technically a 'Configure' area but there was no harm in being able to view the settings for troubleshooting or flagging errors to those who do have admin rights to change settings.

3 Replies 3
alemabrahao
Kind of a big deal
Kind of a big deal

As far as I remember, Observe has always been view-only in areas classified as Monitor.

And Read-only can view the settings.

I think you're confusing things.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
NeilB83
Conversationalist

Thanks. I did check though and its observer and it definitely worked before:

 

https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/M...

 

Roles

View all available roles for your organization or network in the "Roles" tab.

Full Access 
  • (Organization scope): Highest level of access. This gives full administrative access to all networks and organization settings.

  • (Network scope): Network level access gives full administrative access to selected networks.

Observer
  • (Organization scope): Read-only administrative access to the organization without the ability to make any changes. 

  • (Network scope): Access to most aspects of a network, including Configure sections without the ability to make any changes. 

alemabrahao
Kind of a big deal
Kind of a big deal

To be honest, this doesn't make sense, because it's describing the ready-only role.

 

This document seem to be wrong.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels