With Fostr’s Dropbox integration, your team can connect file storage and collaboration directly into the AI operating system. This page explains the credential setup, permission options, and content visibility rules so you can control how Dropbox files are linked, who is able to view or edit them, and how secure access is preserved when those files are used inside Records, Actions, and automated workflows.

Credentials and Access

Fostr connects to Dropbox using credentials generated through the Dropbox App Console. These values allow a secure connection so files and folders can flow into workflows.

The integration requires:

• An App key and App secret (from the Dropbox app setup)
• An OAuth 2.0 access token (user‑level or team‑level depending on the account type)

A single set of credentials is configured at the tenant level, giving all Fostr users consistent access to the connected Dropbox environment. All sensitive values are automatically encrypted and stored within the Integration record. Only administrators and designated stakeholders have the ability to update them, and environment protections keep credentials write‑protected.

When creating the app in Dropbox, be sure to select the correct scopes. In most cases you’ll need:

• File metadata read/write
• File content read/write
• Team or shared folder scopes if working in a business account

Before enabling the integration in production, you can run the setup in a test environment. This step helps confirm tokens are valid, connections are successful, and files ingest properly.

Permissions and Visibility

Once Dropbox is linked, your files and folders can be surfaced in Fostr workflows, making it easier to reference documents or add them to Records and Actions.

Access follows two layers of security:

1. Dropbox permissions always apply first. If the integrated account cannot open a file in Dropbox, it won’t appear in Fostr.
2. Fostr roles control who inside your organization sees the Dropbox content once it has synced.

This means:

• Administrators and a small set of approved roles control the integration itself
• Operators or workflow users only see files tied to the actions or Records they are assigned
• Any restrictions set in Dropbox continue to apply and Fostr does not alter them

The dual model ensures both systems remain in sync. Dropbox defines who can access content, while Fostr ensures only the right internal users see that content in context.

If tokens expire or permissions are changed in Dropbox, the integration will stop syncing. Administrators simply need to refresh credentials in the Integration record to restore continuity.