TYPO3 access review: who can edit what, and what your AI can do

• We want to review who has access to our TYPO3 backend. List every backend user and group, what each may edit (sites, tables, file rights, languages, and whether changes go live at once), which accounts are admins or never used, and what you yourself can do through this connection. Read only, answer here in the chat.
  One question: users, groups, rights, unused accounts and the assistant's own reach

1. Ask once: every backend user and group, what each may edit, which accounts are admins or never used, and what the assistant itself can do. Say that it is read only.
2. The assistant reads the backend users and groups and the permissions of its own connection.
3. On our demo it finds four users and two groups: two admins, one of them TYPO3's system user for the command line, and demo-editor, which has never logged in but may publish live.
4. Per group it lists page trees, tables, editable fields, file rights, languages and modules: both groups reach both sites and may delete files, and neither has a language limit.
5. It ends with what to look at and with its own reach: the connection is an admin, so it suggests connecting as a backend user with narrower rights.

Shown in Claude; other MCP assistants work too.

A question changes nothing: the assistant only reads, so there is nothing to put back. To check, open Administration, Users: the list shows every account with its group, admins with an orange icon. Each group's record shows its mounts and record permissions.

AI Foundation with its MCP server switched on, an MCP-capable assistant, and an admin connection for the user and group tools; AI Foundation is free.

• The user and group tools answer only when the assistant signs in as an admin. Run the review with an admin connection, then connect everyday work as a backend user with narrower rights.
• Passwords and multi-factor settings are never returned, so check multi-factor login for your admins in the backend.
• Permissions set on single pages (owner, group and everybody, in the Permissions module) are not part of this answer. Check them in that module.
• The assistant works with the rights of the backend user who signed in: on Live, its changes are live at once.
• What your assistant reads through MCP goes to the vendor of that assistant, as with any chat.