Invision Community StrawberryThe member work, done and queued for one look
Invision Community exposes 3 operations and a companion can work all of them: update a member, create a member and create a forum topic. Anything that changes a record waits for your click.
Open the member. Check it against something else. Write the change. Move to the next one. That is the Invision Community afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a member until you approve it.
What it can do is exactly what Invision Community exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can update a member, create a member and create a forum topic, and work across the members and forum topics.
The Invision Community API stops at Invision Community. 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 members or ask you for them?
In the tab.
Invision Community exposes no read operation to a connected account, so a companion opens Invision Community in the session you are already signed into and reads the screens you would.
The members are what most of this inventory is about, alongside the forum topics. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Invision Community admin becomes a queue you review.
What happens before it can update member?
All 3 write operations wait for you.
A companion can update a member, create a member and create a forum topic, and each one is staged on an approval card first: you see the member, the field and the new value before it lands in Invision Community.
Nothing in Invision Community is sent, changed or deleted on your behalf without that click, and a rejected card leaves the member exactly as it was. The gate is the same one on every surface, described at security.
- Update Member
- Create Member
- Create Forum Topic
Does the member sweep have to be asked for every time?
Yes.
Saved as a routine, the Invision Community members 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 operations playbook catalogues the other recurring shapes of the messages, the Invision Community members 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