Where Enterprise Ego writes to
Everything Enterprise Ego fetches goes straight to storage you choose. Below you find, per storage, how it connects, which permissions we ask for, what the folders look like and which files appear.
Several storages at once
You can connect more than one storage, for example SharePoint for the team and Amazon S3 as an extra copy. Every active storage receives all conversations, so you keep several copies. One of the storages is primary: your AI reads the shared memory from it, meaning knowledge, contexts and the demo. If one storage fails, the others keep writing and you see the error in the app. As soon as it works again, that storage receives the missed data.
Folder structure
Everything lands unprocessed in the bronze layer, with one folder per employee. If you need to erase an employee's data, for example under the GDPR, you delete that one folder. Inside that folder the path is adjustable with {source}, {yyyy}, {mm}, {dd} and {project}.
bronze/{user}/{source}/{yyyy}/{mm}/{yyyy}-{mm}-{dd}.jsonl
bronze/{user}/{source}/journal-{yyyy}-{mm}.md
bronze/{user}/{source}/bijlagen/{yyyy}/{mm}/{record-id}/{bestandsnaam}
File formats
- JSONL per platform, employee and day. Every line is a record with id, time, source, user, kind, project, summary and the full original response of the platform.
- Markdown per employee per month: a readable journal per conversation with the title, date, source, project and the turns of user and assistant in plain text.
- Attachments as the original file, only for Claude Enterprise, up to the configured size (25 MB by default). On storage that cannot write binary files only the details of the attachment are in the logs.
Every run is idempotent: records are merged on their id, so there are never duplicate lines, even if a run happens again.
Azure Blob Storage
Object storage in your own Azure environment
How it connects
- With a SAS URL (recommended)
- With a service principal
Which permissions we ask for
With a SAS URL: Read, Add, Create, Write and List on that one container (Delete is optional). With a service principal: the role Storage Blob Data Contributor, on that container only.
Steps for the administrator
- Create a storage account in Azure with a container in it.
- Open the container and choose Shared access tokens.
- Give the permissions Read, Add, Create, Write and List and choose a long expiry date.
- Copy the full SAS URL and paste it below.
Amazon S3Beta
Object storage in your own AWS environment
How it connects
- With an IAM role (recommended)
- With an access key
Which permissions we ask for
An IAM role or access key with only PutObject, GetObject, DeleteObject and ListBucket on the bucket and folder. For an IAM role we show the trust and permissions policy to copy.
Steps for the administrator
- Create a bucket in AWS.
- Create an IAM role with the permissions policy below.
- Copy the trust policy below into the role.
- Enter the bucket, the region and the ARN of the role below.
S3-compatibleBeta
Hetzner, Cloudflare R2, MinIO and other S3 storage
How it connects
- With an access key
Which permissions we ask for
A key pair with access to that bucket only.
Steps for the administrator
- Create a bucket and a key pair with access to that bucket only at your provider.
- Look up the address of the storage, for Hetzner that is https://location.your-objectstorage.com.
- Enter the address, the bucket and both keys below.
OneDrive
A folder of its own in your OneDrive
How it connects
- Sign in with Microsoft
Which permissions we ask for
Sign in with Microsoft with only the permission Files.ReadWrite.AppFolder. Enterprise Ego only sees its own folder under Apps.
Steps for the administrator
- Click Connect and sign in with your Microsoft account.
- Give consent. Enterprise Ego gets a folder of its own under Apps.
Google Drive
A folder of its own in your Google Drive
How it connects
- Sign in with Google
Which permissions we ask for
Sign in with Google with only the permission drive.file. Enterprise Ego only sees the folder it creates itself.
Steps for the administrator
- Click Connect and sign in with your Google account.
- Give consent. Enterprise Ego only sees the folder it creates itself.
Dropbox
A folder of its own in your Dropbox
How it connects
- Sign in with Dropbox
Which permissions we ask for
Sign in with Dropbox with the permissions files.content.write and files.content.read. Enterprise Ego gets a folder of its own under Apps.
Steps for the administrator
- Click Connect and sign in to Dropbox.
- Give consent. Enterprise Ego gets a folder of its own under Apps.
GitHub
A private repository on GitHub
How it connects
- With an access token
Which permissions we ask for
A fine-grained token with only the Contents permission on that one private repository.
Steps for the administrator
- Create a private repository on GitHub.
- Create a fine-grained access token that may only read and write this repository (Contents).
- Enter the token and the name of the repository below.
Azure DevOps
A Git repository in Azure DevOps
How it connects
- With an access token
Which permissions we ask for
An access token with the Code permission (read and write).
Steps for the administrator
- Create a Git repository in your Azure DevOps project.
- Create an access token with the permission Code (read and write).
- Enter the token and the details of the repository below.
Beta means the connection has not yet been tested end-to-end against a real environment.
Tip: turn on immutable storage (WORM) or a retention policy on the storage. Then nobody can change the logs afterwards.