Wix Dataset Modes: Read, Write and Collection Permissions

A Wix dataset connects page elements to a CMS collection. Use Read to display stored content, Write to collect new items, and Read & Write when the page needs to display and change content. Collection permissions separately decide who can perform those actions. Both settings must match the job.
For a business owner, the useful question is simple: should this page show information, accept a new entry, or change an existing record? Answer that before changing permissions to get a broken page working.
This guide covers Wix Studio and Wix Editor. Wix Harmony handles CMS connections differently and does not use these datasets. The service catalogue and request examples below are planning examples, rather than client projects.
CodeMasters builds CMS-driven pages and custom workflows through its Wix development service. If your page displays the wrong content or saves to the wrong place, bring the URL, collection name and expected behaviour to a free 30-minute consultation. We can discuss the configuration and development scope.
Choose the Wix dataset mode by the task
Think of a collection as the stored records and a dataset as a connection used by elements on a particular page. A public service list and a private request form can have different connections and access requirements.
Wix's dataset mode guide describes three modes:
Page task | Dataset mode | What to check separately |
Display a service catalogue | Read | Visitors may view the intended public collection |
Accept a new request | Write | The intended visitor role may add an item |
Display and edit an existing member record | Read & Write | The member may view and update that particular record |
Read supports display through connected elements. Write supports new entries through connected inputs, without reading existing content through that dataset. Read & Write supports both directions, subject to the collection's permissions and the page's setup.
Do not choose Read & Write simply because it sounds more capable. A catalogue usually needs no editing controls. A new request usually needs a fresh item, rather than an existing record loaded into the form.
Set up the dataset in Wix Studio or Wix Editor
Use Wix's current dataset setup instructions for the editor you have. The basic setup is the same in both:
Open the relevant page in the editor and select CMS on the left.
Select Add Content Elements.
Add Dataset for a display connection, or Form dataset for a submission connection. Their default modes are Read and Write respectively.
Choose the collection, give the dataset a useful name and select Create.
In its settings, choose the Dataset mode that matches the task.
Connect each page element to the intended dataset and collection field.
Use names that explain the connection, such as Public service list or New service request. This helps the next person distinguish datasets when several are on the same page.
For an existing input, select it, open Connect to CMS, then Dataset Settings to inspect the mode. Before changing it, check the collection selected in the connection panel. A correctly configured dataset pointing to the wrong collection still produces the wrong result.

Wix's dataset settings show the selected collection and the Write mode used to add submissions. Source: Wix Help Center
Check the field and the button, not just the dataset
A form's name input, email input and project description should each connect to the appropriate field. Check the collection's field types as well as their names. A similar label is easy to select by mistake.
For a dataset-connected CMS form, check that its submit button uses the intended dataset's Submit action. Review the success and failure messages too. Wix's input troubleshooting guide covers these checks.
After changing a connection, test the complete page. Enter a clearly marked test request, send it, then find the resulting item in the intended collection. Confirm the actual saved values rather than stopping when the confirmation message appears.
Set collection permissions for the people using the page
Dataset mode describes the connection's behaviour. Collection permissions govern access to the stored content. Changing one does not replace checking the other.
In the dashboard, open CMS. Use More Actions beside the collection, then Permissions & privacy. Wix provides Show content, Collect content and Advanced options. Its collection permissions instructions explain the roles and available actions.
Show content suits material intended for reading. Collect content allows new items to be added. For updates to existing items, review Advanced permissions and the relevant role's Update access. Collect content alone does not grant that update access.
Record four decisions for each collection: who may view, add, update and delete. Make those decisions from the business requirement before selecting checkboxes.
Be careful with Everyone. Wix warns that content with public access can be retrieved through an API even when it is not displayed on the page. Hiding a field, removing a menu link or filtering a repeater is therefore insufficient protection for private content.
For member-specific records, establish which person owns each item and test access with another member account. A Members permission describes a group. It does not by itself express your business rule that each customer should only see their own requests.

Wix's Advanced permissions table separates View, Add, Update and Delete access for each role. Source: Wix Help Center
Keep public service information apart from private requests
Consider a contractor listing renovation services and accepting requests. The service titles and descriptions belong in a public catalogue. Customer names, addresses and project notes belong in a separate collection with access chosen for the enquiry workflow.
The public list can use a Read dataset. A custom CMS request form can use a Write dataset with permission for the intended visitor to add an item. Staff can then manage those requests through an appropriate dashboard role or a separately scoped internal workflow.
This separation makes the access decision easier to review. Someone updating public service copy does not need the request form to read customer submissions. Someone submitting a request does not need to read the earlier entries.
Before building a custom CMS form, check whether Wix Forms meets the requirement. New Wix Forms already supports conditional questions and multiple pages. Our Wix Forms and Velo comparison explains that decision. A dataset-connected CMS form has its own storage and connection setup, so identify which form system you are maintaining.
Avoid fixing a submission problem by opening every permission
A common troubleshooting mistake is to enable broad view and update access until a form starts working. That can disguise the original problem and leave more access than the page needs.
Instead, reproduce the failure and work through the connection in order. Is the input connected to the correct field? Is the dataset in a mode that permits the intended action? Is the button connected to Submit? Does the visitor's role have the required collection permission?
If the form is adding new requests, investigate why it appears to need update access. It may be loading an existing item, using the wrong dataset, or running custom code with a different save behaviour. Resolve that cause before widening access.
Record the original settings before changing them. Make one targeted change, retest and remove temporary access that the finished workflow does not need. Keep the test records recognisable and avoid using real customer details during diagnosis.
Test the published page with the right roles
An owner viewing the page while signed in is a poor substitute for a visitor test. Wix administrators retain broad collection access. Use the published page as a signed-out visitor, then use authorised test member accounts where the workflow requires membership.
Test | Expected behaviour | Evidence to keep |
Signed-out visitor opens the catalogue | Intended public items display | Page and displayed service |
Visitor sends a new request | A new item contains the entered fields | Test marker and saved item |
Member edits an authorised record | Only the intended record changes | Record before and after |
Another member follows the same route | Private records remain inaccessible | Account role and observed result |
Visitor submits an invalid required field | Clear feedback allows correction | Field and message |
Agree the expected outcome before testing. If a visitor is supposed to submit without an account, a login requirement is a failure. If a page is intended for members only, signed-out access should follow that restriction.
Where optional sandbox collections are enabled, also confirm you are checking the live collection used by the published page. Keep test and live data clearly distinguished. Review the saved item and any later notification or integration as separate checks.
For privacy-sensitive records, ask the developer to review collection access and backend logic as well as visible page behaviour. A page test checks the route you exercised. Access decisions need review at the storage and code level too.
Decide what needs Velo development
Displaying a CMS catalogue or collecting straightforward entries can often be configured with native connections. Start there when the requirements fit.
Custom development becomes relevant when the workflow requires an external system lookup, business-specific processing or record access that needs server-side checks. Write down the exact requirement, the data involved and the person allowed to perform each action before commissioning code.
Ask the developer to explain how identity and record access are checked, which fields the browser receives, and what happens when a save or later handoff fails. Broad permissions should not be the solution to an unclear workflow.
If you are still deciding whether CMS content fits the site, read our static and dynamic page comparison. This dataset review is the next implementation decision after choosing how the content will be managed.
Common questions
Why does my catalogue show only some collection items?
Check the dataset's filters, sort order and Items per load setting before changing permissions. The connection may be selecting a subset, or loading only the first group of records. Use a known catalogue item to check which setting excludes it, and test the page's load-more or navigation behaviour if provided.
Can I change Wix Stores or Wix Bookings collection permissions here?
Wix app collections are managed by their corresponding apps. The CMS permission controls described above apply to your own collections. Identify whether you are working with a custom service catalogue or an app-managed collection before following these steps.
How do I tell a dataset name from its ID in Velo code?
The dataset name helps you identify the connection in the editor. The Dataset ID identifies it in page code. Before changing that ID, ask the developer to check references to it. Renaming a connection for clarity and changing an identifier used by code are different maintenance tasks.
For help planning or correcting a CMS workflow, book a free 30-minute consultation with those details, or send the page and requirement. We can discuss whether native configuration is enough and where development is needed.


