You can
use the WriteMetadata (WM) and WriteMemberMetadata (WMM) permissions
to enable someone to interact with a folder's contents, but not update
or delete the folder itself. On the folder, grant WMM and deny WM.
The following list explains
the difference between these two permissions.
provides general control
for additions, deletions, and updates. For example, to edit a report,
you need WM for the report. To delete a report, you need WM for the
report (and WMM for the report's parent folder). For containers other
than folders (such as repositories, libraries, and schemas), WM also
affects adding and deleting child objects. For example, to add an
object anywhere in a repository, you need WM at the repository level.
For folders, adding and deleting child objects is controlled by WMM,
not WM.
WriteMemberMetadata (WMM)
provides specialized
control for adding and removing objects in a folder. You need WMM
on a folder in order to add an object to the folder or delete an object
from the folder. For example, to save a report to a folder, you need
WMM for the folder. To remove a report from a folder, you need WMM
for the folder (and WM for the report).
Tip
We recommend that anyone who
has a grant of WM is not denied WMM.
Tip
If WMM is not directly set
on a folder, the WMM setting mirrors the WM setting. WMM is never
inherited from a parent object.