---
title: "Comala Document Management Data Center | Understand the 'set-restrictions' macro"
canonical: "https://support.appfire.com/space/SUPPORT/540574888/Comala%20Document%20Management%20Data%20Center%20%7C%20Understand%20the%20'set-restrictions'%20macro"
format: markdown
---
## \uD83E\uDD14 Problem

When adding only the macro** {set-restrictions:type=View|group=sample_group} **to the workflow, the sample_group obtains permission to edit the content.

## \uD83C\uDF31 Solution

Comala Document Management integrates with Confluence Permissions and Restrictions. **{set-restrictions:type=View}** removes all view and edit restrictions on the page. When defining **view restrictions** without **edit restrictions**, Confluence doesn’t allow it if 'no one' has edit permissions.

1. To avoid this behavior, it is essential also to specify ***edit*** restrictions on the page.
2. In this case, you should add the macro **{set-restrictions:type=Edit|group=another_sample_group}**
3. Now, Confluence knows who can see the page and edit it.

> ℹ️ Please note that a Confluence Administrator or a Space Administrator can manage the restrictions and add themselves as editors/viewers.

## \uD83D\uDCCE Related articles



> Macro (contentbylabel)