Using ShareBrowser to mount and manage mount points in both macOS and Windows is generally recommended by SNS as the best way to access EVO volumes.

Besides ShareBrowser, both macOS and Windows provide multiple ways to reach network volumes. While alternative methods may not have the ability to leverage harvested metadata and proxies for files, or apply tags/comments to files as ShareBrowser will, they are valid access methods nonetheless. Some of these methods are more efficient than others with regards to accessibility and speed.

macOS

If ShareBrowser is used in the environment, using the ShareBrowser Desktop client is the recommended way to mount and access files, to ensure database consistency for metadata, such as user-added tags/comments.

Accessibility in macOS Finder

Volumes may also be mounted through Finder using Go > Connect to Server and entering smb://network-IP-address and then authenticating with the user credentials for the network volume.

Once mounted, the share is going to likely be available on the Desktop of macOS for direct access to the mounted location. If the share doesn't appear on the Desktop, it may help to go to Finder > Preferences and enable Connected servers to show on the Desktop.

Whether Finder or ShareBrowser is used to originally mount the share, always ensure you're using the mounted volume when browsing its contents, rather than an advertised network location.

Finder methods that are NOT recommended:

If the sidebar in Finder is used to access the volume, by clicking under the Shared heading, the contents for the share can get re-queried each time this is accessed. This means that instead of utilizing the mounted volume's cache to present the list of files and folders, it requests this again from the server. When this happens, it is possible there may be a much longer wait to view the contents. Most delays in file population when accessing a share can be a result of browsing for the share this way, instead of using the mount that is already present on the workstation.

The path to the advertised location may also not be the one that's intended: for example, a workstation may have a dedicated 10GbE link to EVO, while the sidebar location shows EVO's 1GbE connection to the local network. Browsing from the sidebar would use the 1GbE link, and leave the 10GbE connection idle.

Using the Finder sidebar may also create a duplicate mount for network volumes under certain conditions. When this happens, it may cause media linking issues in applications or provide a slower than optimal connection on the workstation.

If there are multiple paths to reach the volume over the network - such as 10Gb and 1Gb - it is possible to inadvertently create a 2nd link to the volume over another IP address.
When more than one NAS protocol is available for a user (SMB & AFP), depending on the version of macOS present, this may create a duplicate mount over the same IP address, but using an incorrect protocol. This can cause various issues with metadata management and file accessibility. It is recommend choosing to allow only one of these two NAS protocols and avoid mixing AFP and SMB when possible.
Utilizing AVIDFS mounts for Media Composer requires Avid emulation on the workstation. Browsing through the sidebar can present a new mount that is strictly SMB in lieu of the AVIDFS mount and cause issues with media linking in Media Composer.

TIP: Once the volume is correctly mounted in macOS, it is subsequently possible to drag and drop the Desktop volume mount to a Finder window - under the Favorites heading. This enables the shortcut to be more easily accessible to users through Finder, as well as through Save and Save As... dialog boxes, while avoiding the Shared sidebar link mentioned above.

Windows

Accessibility in Windows Explorer

It is possible to select a drive letter for mapping the mount, and it's best to keep all Windows workstations using the same drive letter associations for consistency with media linking and everyone's own sanity. It is also possible to map volumes with drive letters through Windows Explorer if ShareBrowser isn't present.

Explorer methods that are NOT recommended:

The mapped drives likely will show up in the Windows Explorer sidebar. These mapped locations may be used to access the volume through Explorer if necessary; however accessing through the advertised IP or host name under the Network heading in the Explorer sidebar can cause less than optimal results.

If there are multiple paths to reach the network volume over the network - such as 10Gb and 1Gb - it is possible to create a 2nd link to the volume over another IP address.
Utilizing AVIDFS mounts for Media Composer requires Avid emulation on the workstation. Browsing through the sidebar can present a new mount that is strictly SMB in lieu of the AVIDFS mount and cause issues with media linking in Media Composer.

None of these access methods are wrong necessarily, but as mentioned above some of these have a better user experience than others.