Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 08:30 UTC
docs: link file expiry dashboard setting
Brendan O'Leary [zen] committed
Oct 21, 2026 at 19:39 UTC
2cd3296cbac8a4417559fdca545fa8bc7ebf8714
3 files changed
+3
-3
docs/content/kb/guide/platform-file-storage.mdx
+1
-1
@@ -13,6 +13,6 @@ aliases: ["/kb/sdk-and-api/composio-file-urls-are-short-lived-staged-downloads",
13
14
When a hosted tool returns a file URL such as `data.file.s3url`, Composio normally stages the bytes in Composio-managed object storage and returns a signed download URL rather than the provider's original URL.
15
16
-The default signed-URL lifetime is one hour and can be configured for a project through its File TTL setting. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
16
+The default signed-URL lifetime is one hour. Organization admins can change it to any duration from 1 second to 24 hours in [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=platform-file-storage) under **Configuration > File download link expiry**. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
17
18
There is no single customer-facing maximum that applies to every tool. Provider limits, the action implementation, runtime memory, and timeouts can impose lower limits, so check the exact action before quoting a hard cap.
docs/kb/articles/platform-file-storage.md
+1
-1
@@ -2,6 +2,6 @@
2
3
When a hosted tool returns a file URL such as `data.file.s3url`, Composio normally stages the bytes in Composio-managed object storage and returns a signed download URL rather than the provider's original URL.
4
5
-The default signed-URL lifetime is one hour and can be configured for a project through its File TTL setting. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
5
+The default signed-URL lifetime is one hour. Organization admins can change it to any duration from 1 second to 24 hours in [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=platform-file-storage) under **Configuration > File download link expiry**. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
6
7
There is no single customer-facing maximum that applies to every tool. Provider limits, the action implementation, runtime memory, and timeouts can impose lower limits, so check the exact action before quoting a hard cap.
docs/kb/source/platform/file-storage/public.md
+1
-1
@@ -16,6 +16,6 @@ tags:
16
17
When a hosted tool returns a file URL such as `data.file.s3url`, Composio normally stages the bytes in Composio-managed object storage and returns a signed download URL rather than the provider's original URL.
18
19
-The default signed-URL lifetime is one hour and can be configured for a project through its File TTL setting. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
19
+The default signed-URL lifetime is one hour. Organization admins can change it to any duration from 1 second to 24 hours in [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=platform-file-storage) under **Configuration > File download link expiry**. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
20
21
There is no single customer-facing maximum that applies to every tool. Provider limits, the action implementation, runtime memory, and timeouts can impose lower limits, so check the exact action before quoting a hard cap.