AI agents can work in authorised accounts, but the access should be as deliberate as the task.
A browser-based agent can use signed-in sites already available in the browser and the apps you explicitly connect, which makes real operating work possible without exporting every detail into chat. The important questions are which account it can use, what it may do there, and where it must stop for your approval.
Browser sessions provide context that exports leave behind.
A signed-in account can contain live status, selected filters, page history, and relationships between records that a spreadsheet export does not capture. Work such as support triage, account preparation, or portal review often becomes slower the moment someone has to reproduce that state somewhere else.
Strawberry can work within the browser context used for the assignment, including signed-in websites available in that browser. It can also use the apps you choose to connect for supported operations.
Access should begin with the smallest useful scope.
Do not grant broad access because a task might become useful later.
Identify the account, the page set, the connected app, and the outcome needed now, then limit the assignment to that context.
A good request also says what not to do. That turns “look at this customer account” into an operational instruction that a person can audit.
Connected apps are explicit, not magical.
When an app is connected, its supported operations determine what Strawberry can do through that integration. For example, the native Gmail integration includes capabilities such as searching mail, retrieving threads and attachments, creating drafts, replying, sending supported messages, labelling, archiving, and trashing mail.
That specificity is useful: it lets a team discuss the actual operation they are authorising rather than treating “AI access” as one vague permission.
Sensitive actions need a named stopping point.
An agent may be able to collect evidence and prepare a response without being allowed to send it. It may identify a record correction without being allowed to save it. The person accountable for the relationship or system should see the destination, content, and effect before a material action happens.
Treat payments, public posts, permissions changes, deletions, and customer communication as especially clear review moments.
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