Can I Use an AI Agent at Work When My Company Restricts the Data I Can Connect?
A participant asked how company rules shape connecting an AI agent at work. My answer was two moves, and one thing the recording cannot tell you.
Practice on a dummy account first. I said it's a great way to be comfortable with the level of access you're giving a system. When you're ready to ask at work, bring the vendor's privacy policy, security link and Trust Center to the person who decides, and send enterprise questions to the vendor's own team. I can't tell you what your company allows.
On October 7, 2026 a participant described the gap you may be in: a lot of freedom with an AI agent for personal use, and restrictions when it comes to enterprise data at work. They asked how company policy and security rules shape the way I connect at work, compared with my own business (49:27). I answered with the vendor's documents and where to send enterprise questions. I didn't answer for any one company's rules, so I'll stay with what I said.
Where do you start if your company limits what you can connect?
With an account that holds nothing from your company. Earlier in the session a participant asked whether they could build with a dummy Gmail account to practice. My answer was absolutely (19:31). Then I gave my reason:
From the recording, 19:58. it's a great way to be comfortable with the level of access that you're giving to a system.
I called it an extra step. I also pointed out that most of us have an email account where promotional and spam email lands, and that's the account to use to get started (20:08). For the steps that keep the access small once you do connect something, read How Do You Practice With an AI Agent Without Risking Real Data?.
What do you bring to the person who decides?
The links come first. Before we built anything on October 7, I told the group there are two common questions, privacy and security, and that I had put the vendor's policy on both in the chat (6:23). When a participant asked whether they could just watch, I pointed back to that:
From the recording, 18:50. this is exactly why we pasted the links for the privacy policy as well as the security protocols
Then I described what the vendor put together for reviewers:
From the recording, 50:31. One of the things that they put together is their trust center screen. If you're looking at my screen now, you have this link in the chat, you can screenshot Gumloop's security email account, but they also provide a compliance review.
On my relationship to Gumloop, I said this:
From the recording, 33:22. I don't work for Gumloop. I found this tool over the summer through Lenny's podcast, and I started using it and have since made myself an ambassador for them. I've created a relationship with Gumloop. I am not an employee.
More on that answer: Do you work for Gumloop? (the answer from the session).
Gumloop's Trust Center page shows a security email address, a compliance overview and documents you can request access to. Checked on 2026-11-05 against Gumloop's Trust Center. I don't read the compliance details out for you here. Open that page and read what it lists on the day you ask, because it's the vendor's page and it changes. For the same material seen from a legal team's side, see How Do Enterprise Legal Teams Start Vetting an AI Agent Platform?.
Who answers the enterprise questions?
The vendor's team, not me. When the participant asked about enterprise rules, this is what I said about who answers:
From the recording, 50:19. I typically hand that over to the Gumloop team because I am not an employee of Gumloop, but I have shared the privacy policy and the security link.
I added that their team can walk you through the rest (51:10). Your reviewer will also have questions about your own company's rules, and those I can't answer. Take the questions that are about the vendor to the vendor's team.
What goes wrong
I didn't name a failure for this question. What I did say is that the practice account is an extra step (19:58). I answered a participant about the vendor's materials. I didn't tell them what their employer allows.
Where this comes from
This article grows from the session I taught live with Women Applying AI on October 7, 2026. The quoted passages are my own words, taken verbatim from the recording. The steps, tables and checklists around them were drafted by my team's AI agents from those words and my published pages, and checked against the recording before publishing. Platform facts that have a public source carry the dated line above, and screens change.
Build Your First AI Agent in One Hour: the full session with the clips, the prompts and the transcript.
Related reading: What Is AI Governance?, How Do You Practice With an AI Agent Without Risking Real Data?.
Frequently asked questions
Can I use an AI agent at work if my company limits what I can connect?
The recording doesn't say what your company allows. What I said on October 7, 2026 was to practice on an account you're comfortable with, share the privacy and security links, and send enterprise questions to the vendor's team.
What do I bring to IT or security?
The vendor's privacy policy and security link, which I put in the chat for the group (6:35), and its Trust Center page, which I showed later (50:31). Then your own questions about your own data.
What account do I practice on?
My advice was a dummy account, and the account where promotional and spam email lands is a good place to get started (20:08).
Build something that actually runs your workflow.
A focused, free 60-minute live session with Jacqueline. You build alongside her, on your own real task, and leave with an AI agent that is already running.