---
title: "Multiprotocol Best Practices and Limitations"
slug: "multiprotocol-best-practices-and-limitations"
tags: ["5.5"]
updated: 2026-10-27T23:00:54Z
published: 2026-10-27T23:00:54Z
canonical: "docs.vastdata.com/multiprotocol-best-practices-and-limitations"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Multiprotocol Best Practices and Limitations

## Views on the Same Path

If there are multiple views on the same path, including views on nested paths, all of their view policies must have the same security flavor.

## Nested Views

It is possible to create different views on paths that are nested under each other. For example, you can have a view on the path */a/b* and another view on the path */a/b/c*. Each view can use a different view policy.

This is useful, for example, if you want to give a larger set of NFS client hosts read/write access to the higher level directory while giving a subset of NFS client hosts read/write access to a deeper directory.

However:

- It is not recommended to set any multiprotocol behavior settings (such as *path length limit* or *allowed characters* which are options you can set in the view policy), on a child directory's view that are different to the security settings of its parent directory's view, since this could result in unpredictable behavior with permission authorization.
- S3 bucket views cannot have other views nested under them or on the same path.
- If a view has NFSv4 enabled as a protocol, then all views located above that view must also have NFSv4 enabled.

## Multiprotocol File Access

When you enable the SMB protocol on a view together with NFSv3, NFSv4.1 or S3, non-simultaneous access to any files in the view from all enabled protocols is fully supported by default.