# Grok Bot: per-Bot file/folder and database permission isolation on the same account

**URL:** <https://forum.cursor.com/t/grok-bot-per-bot-file-folder-and-database-permission-isolation-on-the-same-account/172724>\
**Category:** Feature Requests\
**Tags:** security, grok-bot\
**Created:** [September 23, 2026, 2:44am UTC](https://forum.cursor.com/t/grok-bot-per-bot-file-folder-and-database-permission-isolation-on-the-same-account/172724 "2026-09-23T02:44:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tony\_Fenwick](https://avatars.discourse-cdn.com/v4/letter/t/ad7895/32.png) [@Tony\_Fenwick](https://forum.cursor.com/u/Tony_Fenwick)\
**Post date:** [September 23, 2026, 2:44am UTC](https://forum.cursor.com/t/grok-bot-per-bot-file-folder-and-database-permission-isolation-on-the-same-account/172724/1 "2026-09-23T02:44:19Z")

</div>

### Feature request for product/service

Cursor Web

### Describe the request

## Problem

Today, all Grok Bots under one Cursor account share one cloud computer. Files, folder trees, browser logins, and connectors are available to every Bot. Official docs correctly say not to treat separate Bots as a security boundary.

I want to run several role Bots on one account (inbox, ops, research, sales, etc.) with hard least-privilege boundaries, not just persona text.

## Request

Please add configurable per-Bot permission isolation for the same account, including at least:

1. Documents / folders — grant Bot A access only to specific paths or project folders; other Bots cannot read/write them.
2. Databases / data stores — grant Bot-scoped access to specific DBs, schemas, or tables (or connector scopes that enforce the same).
3. Ideally extend the same model later to connectors and browser sessions; file/folder + database access is the priority.

This needs real enforcement (not prompt-only instructions).

## Why it matters

Without this, the only real isolation is a separate Cursor account. Soft rules in a Bot persona are not enough for multi-Bot workflows that touch sensitive docs or production data.

## Related

- [Grok Bot: ship real session fences — bots are not a security boundary](https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476)
- [Grokbot Security Isolation / Prompt Injection Protection](https://forum.cursor.com/t/grokbot-security-isolation-prompt-injection-protection/169955)

Thanks.

---

<div class="post-metadata">

**Author:** ![Cristian\_nunez](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@Cristian\_nunez](https://forum.cursor.com/u/Cristian_nunez)\
**Post date:** [September 26, 2026, 9:06am UTC](https://forum.cursor.com/t/grok-bot-per-bot-file-folder-and-database-permission-isolation-on-the-same-account/172724/6 "2026-09-26T09:06:36Z")

</div>

This post was flagged by the community and is temporarily hidden.