OneLogin StrawberryUpdate user in OneLogin, on your say-so
OneLogin exposes 3 operations and a companion can work all of them: update an user, revoke user sessions and create an user. Anything that changes a record waits for your click.
Open the user. Check it against something else. Write the change. Move to the next one. That is the OneLogin 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 OneLogin exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can update an user, revoke user sessions and create an user, and work across the users and user sessions.
The OneLogin API stops at OneLogin. 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.
Does it read the users or ask you for them?
In the tab.
OneLogin exposes no read operation to a connected account, so a companion opens OneLogin in the session you are already signed into and reads the screens you would.
The users are what most of this inventory is about, alongside the user sessions. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of OneLogin admin becomes a queue you review.
What happens before it can update user?
All 3 write operations wait for you.
A companion can update an user, revoke user sessions 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 OneLogin.
Nothing in OneLogin 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
- Revoke User Sessions
- Create User
Does the user sweep have to be asked for every time?
Yes.
Saved as a routine, the OneLogin 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 OneLogin 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