Keycloak StrawberrySomeone still has to update user. It does not have to be you
A companion works the 4 operations your Keycloak account exposes. It can update an user and delete an user, and every one of those waits on an approval card showing the user before it changes.
Open the user. Check it against something else. Write the change. Move to the next one. That is the Keycloak afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a user until you approve it.
What it can do is exactly what Keycloak exposes to an account you authorise and nothing beyond it: 4 operations, 1 read and 3 writes. In practice that means it can update an user, delete an user and create an user.
The Keycloak API stops at Keycloak. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the users come from?
1 of the 4 operations is a read.
Your account, not a guess at it: a companion can get an user, and the full list below is the whole list, with nothing inferred from Keycloak's documentation.
The users are what most of this inventory is about, alongside the users. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Keycloak admin becomes a queue you review.
- Get User
Can it change a user without asking?
All 3 write operations wait for you.
A companion can update an user, delete an user and create an user, and each one is staged on an approval card first: you see the user, the field and the new value before it lands in Keycloak.
Nothing in Keycloak is sent, changed or deleted on your behalf without that click, and a rejected card leaves the user exactly as it was. The gate is the same one on every surface, described at security.
- Update User
- Delete User
- Create User
Can the users pass run every Monday?
Yes.
Saved as a routine, the Keycloak users pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Keycloak users sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents