How do I let my team maintain weclapp custom attributes with AI, without general write permission?

Almost every weclapp system carries fields that exist in no standard: the project number on the ticket, the approval level on the order, the link to the wiki on the customer, the internal tag on the article. Custom attributes are where an ERP fits your own business. That is exactly why they are maintained constantly, and exactly where an AI assistant can help.

The problem: too little or too much permission

If you want to allow a team member to set the custom attribute “Project number” on the ticket, the general write path gives you only a coarse choice: with the permission to write, the person can also change every other field of that ticket. Whoever sorts tickets should be allowed to maintain tags, but not rewrite assignees, customers or status.

The solution: maintaining custom attributes as its own permission

wals.pro AI 4 weclapp has its own permission for this: “Maintain custom attributes”. You find it in the role templates, and in custom roles you grant it individually, independent of the general write permission.

The process stays as wals.pro AI provides for every change:

1. The assistant reads the record and shows you the custom attributes that are set, with their labels.
2. You say which field should get which value or be cleared.
3. The assistant shows a preview: before, after, field by field.
4. Only after your yes is anything written. Afterwards it reads back to check that exactly that arrived.

This works wherever custom attributes live in day-to-day work, including tickets and tasks, contacts, quotations, orders and invoices, articles, shipments and goods receipts.

On items as well

Many custom attributes live not on the document but on its items: the batch specification on the order line, the cost center on the invoice item, the note for installation on the quotation item. Your assistant maintains these too, for the common document types such as quotations, orders, invoices, purchase orders and performance records, whether the document is still in progress or long since booked. Only the named field of the named item changes. All other items, quantities, prices and totals stay as they are, and that is read back after writing. Items of production orders and contracts are not included.

Why the check before writing matters

With custom attributes, weclapp accepts a lot without objecting, including values that never take effect. A date in the wrong format, a selection that no longer exists, a value in the wrong field: the response looks like success, and afterwards there is nothing new in the record.

That's why wals.pro AI checks every value against the field's definition before you approve:

• Selection fields accept only options that are active.
• Dates are stored as they appear in the calendar, without a shifted day.
• Links must be real web addresses.
• Fields that may only be read or that are switched off stay untouched.

After writing, it reads back: are the new values in, and are all other custom attributes unchanged? If not, the system says exactly that instead of claiming success.

Required fields that block every change

An empty required custom attribute has a side effect in weclapp that costs a lot of time in day-to-day work: as long as it is empty, the whole record can no longer be changed, not even somewhere completely different. The error message then names a technical identifier that nobody can make sense of.

wals.pro AI detects this state before writing. The assistant tells you which required fields are still missing, asks for the values and sets them in the same step. If the block comes back from weclapp anyway, it is translated into an understandable instruction.

What explicitly does not happen

• No change without approval. Preview, yes, and only then the write.
• No silent overwrites. If the record has changed since the preview, nothing is written. The assistant reads again and shows a fresh preview.
• No detour to more permissions. The permission allows custom attributes and only custom attributes.

The labels of your fields are also data for the assistant, not instructions. What a field name says does not steer it.

Who this is for

For teams that have adapted weclapp to their business with their own fields and no longer want to click through those fields by hand. And for admins who want to grant permissions as narrowly as the task requires. Maintaining custom attributes isn't tied to any particular plan; on the free plan it counts toward the limited monthly write quota. You define which roles may do it in the roles. You can find more on roles and permissions in the help article Team.

You can find what else wals.pro AI 4 weclapp can do on the product page and in the overview of the weclapp MCP server. Connect wals.pro AI to your weclapp at ai.wals.pro or book an appointment at wals.pro/termin, and we'll show it to you on your own system.