Skip to content
RebelCore Docs

RebelVault

RebelCore Agent can use two kinds of file context:

  • Personal files that you own or that someone explicitly shared with you.
  • Dataset-associated files available through a project and selected dataset.

These paths have different access controls and remain visible as different grants.

Personal working files

Use the paperclip beside the chat box to add a private working document.

Supported personal document formats include:

  • .txt and .text
  • .pdf
  • .docx
  • .pptx
  • .md and .markdown

The established file service can also process supported spreadsheet formats for personal search, but use Add Data when the source should become a governed module or project dataset.

Each file may be up to 20 MB. After upload, RebelCore extracts text, stores the original in tenant storage, creates chunks, and schedules vectorisation. Agent can retrieve the file after processing completes.

Dataset-associated files

Documents added through Add Data may be associated with a file-only or mixed dataset. If you can access its project and select the dataset in Agent, you can question its AI-enabled files.

  • No personal share is required.
  • The dataset’s LLM exposure remains attached to the file-questioning path.
  • Removing project access removes the derived file access.
  • Questioning access does not automatically grant download of the original.

Choose file scope for a question

Open Agent settings:

  • Allow File Content enables or blocks all file search for the request.
  • User files (personal) includes or excludes files you own and files directly shared with you.
  • Selected dataset-associated files remain eligible when User files (personal) is off.

This lets you ask a dataset-only question without accidentally retrieving a local working file. If Allow File Content is off, Agent cannot use either personal or dataset-associated file content.

Sharing personal files

Owners can share a personal file with an active user in the same organisation or with the whole organisation. Recipients may search an AI-enabled shared file, but only the owner can delete it or revoke its direct shares.

Sharing a personal file does not attach it to a dataset. Governed dataset ingestion happens through Add Data.

Security and privacy

  • Original files and metadata remain in the customer’s tenant storage and database.
  • Tenant, user, project, dataset, and file scope is injected by RebelCore, not chosen by the language model.
  • Search results must match an active ownership, direct-share, organisation-share, or selected-dataset grant.
  • The most restrictive applicable dataset exposure governs the final answer.
  • Personal-information masking still applies according to the session settings.

If Agent cannot find a file

Check that:

  • file processing completed;
  • Allow File Content is enabled;
  • User files (personal) is enabled when asking about a personal/shared file;
  • the relevant dataset is selected when asking about a dataset-associated file;
  • you still have access to the corresponding share or project.