Authority Matrix save failure: legacy disabledActions rejected by current validator | FIXED

Teable Discussions
1

FIXED

Hello Teable Support,

I’m encountering an Authority Matrix compatibility issue

The live Authority Matrix export contains these legacy disabledActions identifiers:

updateRecord
createRecord
deleteRecord
copyRecord

The current Authority Matrix validator accepts only the canonical identifiers:

record|update
record|create
record|delete
record|copy

When I try to save the Authority Matrix in the UI, validation fails with errors such as:

Validation error:
Invalid input at "tables[0].disabledActions[0]"
...

The CLI produces the same issue:

Invalid "deny" action "updateRecord" for table tbl47prG84ulbIycnOI.
Allowed: ... record|update ... record|copy

Both authority diff and authority apply --dry-run fail before producing an inspectable comparison. The UI also rejects the entire matrix when I attempt an otherwise unrelated membership change.

Observed details

  • The issue affects the stored Authority Matrix role rules, not table fields or record data.

Thank you.

UPDATE: | FIXED
PASS: the Authority Matrix compatibility repair is live.

Note: I fixed it via the API with a simple AI prompt.
You guys are amazing and the timeliness of the new matrix tool is epic. Teable just keeps getting better and better. THANK You!!!

New permission matrix configuration tool: Export, edit, preview, compare, validate, and apply permissions via CLI with anti-lockout protection.

2

Hi, @Mal

Thank you for the detailed information. Teable’s Authority Matrix does not generate updateRecord, createRecord, deleteRecord, or copyRecord; it uses the record|... format instead.

Could you help us trace where these values came from and how they were generated? This will help us determine how unsupported values entered the Authority Matrix configuration.