CMS: Changing Your Collection Permissions

Allow the collection content to be viewable on the live site by site visitors. This also prevents visitors from adding new items or updating existing items. 

Note: With these 'Show content' collection permissions, admins and collaborators with CMS access maintain full access to the collection. They can perform all actions, including viewing, adding, updating, and deleting collection content, whether from the live site or the CMS itself.

Allow visitors to add content as new collection items via input elements on the live site or API. This permission does not allow visitors to update the contents of existing items. Use the Advanced permissions if you want to allow visitors to edit existing items. See the FAQ section below for more information. 

Note: With these 'Collect content' collection permissions, admins and collaborators with CMS access maintain full access to the collection. They can perform all actions, including viewing, adding, updating, and deleting collection content, whether from the live site or the CMS itself.

With the 'Advanced' permissions, you can select different permissions for viewing, adding, updating, and deleting content for each role. This lets you control what people with each access level can do with your site's collection content. 

For each user role, select the checkboxes to choose whether they can view content, add new items, update existing items, or delete items. You can also create permissions for specific collaborator roles for greater control over which collaborators can view, add, update, or delete items. 

In the table, you can choose from the following access levels for each role: 

Note: With these 'Advanced' collection permissions, admins and collaborators with CMS access maintain full access to the collection. However, you can set permissions for specific collaborator roles to restrict them from having view, add, update, or delete access to the collection. 

The 'Advanced' collection permissions allow you to set specific access levels (View, Add, Update, and Delete) for different roles. Select the checkboxes that represent each access level next to each role to define what people with the roles can do. 

You can also set specific permissions for each collaborator role that grants access to the CMS. By default, selecting checkboxes next to the main Collaborator role gives all CMS collaborators the selected access level. However, 'Advanced' permissions give you granular control to fine-tune what each different collaborator role can do. 

For example, you might want a specific collaborator role to have all the permissions, while all other collaborator roles have only 'View' access. You could set permissions for a specific 'Content Writer' role and select all the permissions for that role. Then, only select the View access next to the main Collaborators role. As a result, your 'Content Writer' collaborators would be the only collaborators that can manage the collection content. 

Keep in mind that admins always maintain full access to your collections. Admins can perform all actions, including viewing, adding, updating, and deleting collection content, whether from the live site or the CMS itself.

There are several preset roles you can assign to collaborators that grant them admin access, including the 'CMS Admin' role. In your collection permissions, when you set permissions for a specific role, you can select roles that grant CMS access under Roles with CMS access. Under CMS Admin roles (included), you can view all the admin roles that maintain full access to your collection. 

When creating a custom role, select the CMS Manage Content permissions to grant collaborators access to the CMS. 

Select any of the following permissions to give a custom role full admin access to all your collections: 

You can control which collections are visible to your site collaborators in the CMS by using the 'Advanced' permissions settings. 

In the 'Advanced' permissions table, set permissions for specific collaborator roles. Then, uncheck the 'View' permission next to the roles that you want to hide the collection from. You can select or deselect the 'Add', 'Update', and 'Delete' checkboxes to further adjust the access levels of your collaborators. 

This ensures that collaborators only see the collections relevant to their tasks, simplifying their navigation and protecting sensitive information.

Tip: This method is useful for hiding collections with sensitive information, such as user submissions, from collaborators who do not need access to that data.

No. The 'Collect content' permission allows people to add content as new items in the collection. It does not allow visitors to update the content of existing items.

If you want to allow visitors to update the field values of existing items, use the 'Advanced' permissions. In the 'Advanced' permissions, select the 'Update' checkboxes next to the relevant roles so visitors can update the field values of existing collection items.

Learn more about creating a custom form with input elements that submit to your collection.

Custom roles allow you to give collaborators tailored access to the CMS and other areas of your site. Admin roles, on the other hand, provide unrestricted access to the CMS and full control of site management. Custom roles automatically become admin roles when any of the following permissions are assigned:  

No, admin roles always grant unrestricted access to the CMS, in addition to other areas of your site. To avoid giving full CMS access, ensure you do not assign permissions that elevate a custom role to admin status.

In your site's Roles & Permissions settings, you can add roles that give collaborators access to your CMS collections. These CMS access roles, by default, have all the collection permissions to view, add, update, and delete items. However, you can fine-tune their access levels for each collection in your collection permissions. 

Keep in mind that CMS admin roles always maintain full access to your collections. This means CMS admins can perform all actions, including viewing, adding, updating, and deleting collection content, whether from the live site or the CMS itself.

Collection permissions allow you to define what people can do with a specific collection's content. You can define different access levels for each type of user. This includes everyone who can view your site, site members, collaborators with CMS access, and even specific collaborator roles. 

Different types of users interact with your collection content in different ways, depending on the permissions you grant. While some actions are restricted to the live site, others extend to the CMS backend for collaborators. Here's how collection permissions work for each group of users:

No, you cannot edit permissions for Wix app collections. You can view these collections in your CMS, but you cannot modify them there. Wix app collections get their content from the corresponding apps (e.g. Wix Stores, Wix Bookings). Manage the content of these Wix app collections from the apps themselves. 

No, you cannot edit the permissions Wix Blocks collections. Go to Wix Blocks to modify the content of your Blocks. 

By default, new collections you create are set to Show content with Everyone allowed to view content.