Organize around the work
Group files in buckets and nested folders. Rename and move folders as your process evolves, while keeping the organization meaningful to the people and systems using it.
ART Datalake / Storage
A place for every file. A clear path to the work.
Files are part of the workflow, not an afterthought. Keep incoming documents and generated outputs organized so applications and agents can work with the right material in the right environment.
Storage in practice
Built for the way your data works.
Connect a defined workspace
Bind a storage connector to a bucket and, when needed, a base folder. Give a workflow a clear working area rather than asking it to navigate unrelated files.
Choose access and lifetime
Keep custom buckets private or explicitly make them public when the use case calls for it. Configure retention for custom buckets and review changes through audit history.
Illustrative workflow
From supplier documents to a review package
An onboarding workflow reads a supplier brief from its assigned folder and writes a review summary alongside it. The team keeps the source and output organized together, while bucket retention defines their lifetime.
- Organize the source folder
- Connect the approved workspace
- Store the generated result
Understand the lifecycle.
Custom buckets default to indefinite retention. Protected system buckets have product-managed access and lifecycle rules. Expired objects become unavailable before background cleanup removes the stored bytes.
A few useful details.
Can files be shared publicly?
Custom buckets can be explicitly made public. Switching a bucket back to private revokes its public URLs. System buckets cannot be made public.
Can a connector be limited to one folder?
A storage connector can define a base folder within a bucket. Its file operations stay within that working area.
Start with your workflow
What should your data make possible?
Bring the records, files, and context behind your process. We’ll explore how Datalake fits.