M‑Files forms for colleagues who rarely use it
CtrlPortals gives each kind of object in M‑Files a short form: the fields a task needs, with instructions beside them and the next step in its workflow. Whoever does the task twice a year sees what to fill in. Any M‑Files edition, cloud or on-premise.

The task that comes round twice a year
A visit to prepare, a complaint to answer, a returned order to inspect, a supplier to rate. The work belongs in M‑Files, beside everything else about the customer or the supplier, but the colleague who does it opens M‑Files a few times a year. By the next time, it is easy to forget which fields matter.
In each case the object is already in M‑Files. A form on it, made for that one task, asks only what the task needs and says how to answer, so the manager who reads the answers gets every one back filled in the same way.
A form that explains itself
Your administrator builds a portal for each kind of object, and the form on it asks only what that task needs, in your company's own words.
A line on what to do
Steps written out, a picture or a short video sit above or beside the fields, so the instructions are on the screen where the work is done.
Your words, your order
Fields carry the labels and the order your company uses, grouped under headings that fold away, in two columns where the form is wide enough.
Answers that steer the form
A field shows up, turns required or locks as other answers change, so a question is asked only when it applies.
Sent on from the same screen
When the form is done, the object moves to its next workflow state from the portal, with a comment where your process asks for one. Only the steps that apply are offered.
Asked before anything is lost
Someone who moves to another object or closes the portal with changes unsaved is asked whether to save them, discard them or go back.
Within each person's rights
The form reads and saves as the person using it, under their own M‑Files rights, exactly as far as the vault allows them.

A new contact, added from the form
Some fields point to another object: the company a visit is for, the people coming, the contact who reported a complaint. When the one a field should point to is not in M‑Files yet, the person filling in the form adds it from that field and carries on.
- The name carries over — The name typed into the field is filled in on the new contact or company, ready for the rest of its details.
- Linked as soon as it is saved — Once the new object is saved, the field points to it.
When two people answer at once
A complaint can be with two people at once: the one who logged it and the one who answers it. When both have it open and both save, the second save stops and shows what the colleague changed.
- Their version beside yours — For each field, the portal shows the value when you opened the object, the value now with who saved it and when, and yours. You overwrite, keep theirs or go back to the form.
- One value, however many forms — A portal can show the same field in two forms or on two tabs. An edit in one shows at once in the others, and the save writes it once.

Three tasks people do a few times a year
Any kind of object in M‑Files can have a portal and a form of its own. Three examples of tasks that come round now and then.
A visit to prepare
Reception books a supplier's team in, and the visit goes to the project engineer who hosts them twice a year. Its form asks for the people coming, the areas they will see and, once the production floor is on the list, who gives the safety briefing. Reception reads the same object the day before.
A complaint to answer
An account manager answers a handful of complaints a year. Customer service logs each one, and the form shows what the customer reported, then asks for the agreed action and the date the customer hears back. When it is done, it moves on to Answered from the same screen.
The yearly supplier review
Purchasing asks every budget holder to rate their suppliers once a year: delivery, quality and paperwork, each Good, Acceptable or Poor. A Poor score makes an agreed action required, so each review comes back with the same fields filled in.

Your own metadata card, inside the portal
Your administrator may already have set up the M‑Files metadata card: its groups, the order of the fields, which ones are required or read-only, and values a rule fills in. CtrlPortals can draw that card inside the portal, with the look of its other forms.
- The card's own rules — Required fields, read-only fields and values set by rule work as they do on the card in M‑Files, with its conditions read the same way.
- A field the form leaves out — Where your administrator allows it, people can add a property the form does not show, and remove one where the M‑Files card would let them.
What it needs to run
- Any M‑Files edition, in M‑Files Cloud or on-premise, with M‑Files 25.1 or later on the server and in the clients.
- CtrlPortals, which the forms come with, and an M‑Files licence for each person who uses them.
- M‑Files Web, or either M‑Files desktop client, new or classic.
- A portal for each kind of object the forms are for, set up in M‑Files Admin.
Your administrator builds the portals and their forms in M‑Files Admin. Fields, groups, columns and rules are described in the CtrlPortals documentation.
Questions about forms in M‑Files
Do the forms work in M‑Files Web?
Can a form create new objects?
Who sets up the forms?
Can we use the metadata card we already have?
Can one answer change the rest of the form?
Is it a separate product?
More ways to make M‑Files fit the job
All of CtrlPortals
Dashboards and boards beside the portals, set up around your own objects.
See CtrlPortalsA friendlier M‑Files
A portal for each kind of object, with instructions and buttons beside its fields.
Read the postCalendar for M‑Files
Visits, reviews and deadlines on a month, by the dates the objects carry.
See the calendar