If you want to implement a custom export policy, you require additional information about how export policies work and how to implement them. This information is available in other guides.
For volumes that contain CIFS shares, the default export policy might meet your requirements. If it does, you do not have to create a custom export policy, and do not require additional information about how to configure one.
A default export policy with a single rule is created and applied to the root volume of the Vserver when you create a Vserver in System Manager. This default export policy permits access to any client, using any access protocol, including CIFS. Users are granted read-only and read/write access, but no one is permitted root access.
For volumes that contain CIFS shares, an open export policy like the default policy is appropriate if you control access to data on the volume using Windows-based authentication and share level access controls.
Sometimes you might want to implement a custom export policy that is more restrictive than the default policy. For example, if you permit both NFS and CIFS access to a volume, you might want to create a custom export policy with separate rules for NFS and CIFS clients.
If you choose to create a custom export policy, you should see the following guides for more information so that you can implement the policy correctly: