Connecting drives

Connect external drives to AI Hub to expand your available storage space for AI Hub projects and conveniently maintain and upload files from your own storage.

Commercial organizations can additionally use connected drives as a location to save processed AI Hub files, including Build project files, Converse conversation files, and app run results.

All AI Hub accounts also include up to one terabyte of storage on Instabase Drive for AI Hub projects and documents. Regardless of your total available storage space, AI Hub is still subject to certain upload limits:

  • Files up to 50 MB or 800 pages.

  • Up to 100 MB per upload batch.

  • Up to 100 documents per conversation.

See limitations for complete information.

Workspace and organization drives Commercial

External drives can be connected at the workspace or organization level. Drives connected at the workspace level are available only within that workspace and all members of the workspace can access files on the drive. Drives connected at the organization level are available to all workspaces in the organization and all members of the organization can access files on the drive.

Info

For commercial members, the contents of any external drive connected to your personal workspace from the My Hub tab are available only to you.

While any drive that’s accessible in the workspace can be used as a source of input files, processed files are saved to the workspace’s default drive, unless otherwise specified.

Connecting drives

You can connect the following types of external storage:

To connect a workspace drive:

  1. From the My Hub tab, select the workspace.

  2. In the Drives section, click the + (plus sign) icon, and select Workspace drive.

  3. Select a drive type.

  4. Follow the configuration steps for the selected drive type.

    Tip

    You can also connect workspace drives directly from the file picker when uploading files to a conversation, project, or app. If you select Browse external drives and no drives are connected to the current or selected workspace, an Add drive option displays.

To connect an organization drive:

  1. From the Settings page, select the Drives tab.

  2. Click + Add Drive.

  3. Select a drive type.

  4. Follow the configuration steps for the selected drive type.

Warning

When connecting external storage, the connection isn’t validated. This means you can successfully connect a drive to AI Hub, then later encounter an error when attempting to perform file operations on the drive. Until drive validation is fully supported, it’s important to correctly input all drive configuration details.

Google Drive

You can connect a Google Drive and upload files from your own and shared drives on the parent drive. In addition to standard file types, AI Hub supports uploading some Google-native file types, specifically Google Docs (.gdoc), Google Sheets (.gsheet), and Google Slides (.gslides).

There are some limitations when using Google Drive as a connected drive:

  • Google Drive is not supported as a default drive and can be connected at the workspace level only.

  • App run results can only be exported to the My Drive on the connected Google Drive, not to any shared drives on the Google Drive.

  • Files and folders with a / in the name don’t appear in the file picker and might result in an error if uploaded by API.

  • Files or folders with the same name don’t appear in the file picker and might result in an error if uploaded by API. This constraint applies in the following scenarios:

    • Two or more files with the same name and same parent folder.

    • Two or more folders with the same name and same parent folder.

    • A file and folder, or several files and folders, with the same name and same parent folder.

To connect a Google Drive:

  1. In the drive selection dialog, select Google Drive.

  2. Enter a name for your drive.

  3. Click Connect to Google Drive.

  4. Select and sign in to the Google account with the Google Drive you want to connect.

  5. Click Allow to grant AI Hub the necessary permissions (see, edit, create, and delete).

AWS S3 bucket Commercial

Connecting to your AWS S3 bucket requires an AWS IAM access key with the following permissions:

s3:DeleteObject
s3:DeleteObjectVersion
s3:GetObject
s3:GetObjectAcl
s3:GetObjectVersion
s3:PutObject
s3:PutObjectAcl
s3:PutObjectVersion
s3:ListBucket
s3:ListBucketMultipartUploads
s3:ListMultipartUploadParts
s3:AbortMultipartUpload

When connecting an AWS S3 bucket, the following settings are available:

Setting Required Value
Name your drive Required A name for the connected drive.
Description Optional A description of the connected drive or any relevant details.
Access key ID Required Your AWS Identity and Access Management (IAM) key.
Secret access key Required Your AWS IAM secret key.
Bucket name Required The name of the S3 bucket to use for file storage.
Region Required The region code for your AWS account, such as us-east-1.

For a full list of region codes, see the AWS Regions and zones documentation.
Path to drive Optional A file path to a folder in the S3 bucket where the desired input files are found. Leave empty to accept default (root).
Server-side encryption type Optional Select the server-side encryption type.

- None: (Default) No server-side encryption.
- SSE-S3: Use Amazon-managed server-side encryption of files.
- SSE-KMS: Use Amazon Key Management Service (KMS) for server-side encryption of files.
Server-side encryption KMS key ID Visible and required if Server-side encryption type is set to SSE-KMS. The Amazon resource name (ARN) for the KMS key.
Note
See the AWS Finding the key ID and key ARN documentation for more information.

To connect an AWS S3 bucket:

  1. In the drive selection modal, select AWS S3 Bucket, then click Next.

  2. Enter a name for your drive and, optionally, a description.

  3. Enter your access key ID.

  4. Enter your secret access key.

  5. Enter the name of the S3 bucket.

  6. Enter the AWS region of the bucket.

  7. (Optional) In the Path to drive field, define a file path to a specific folder within the bucket.

  8. (Optional) Select a server-side encryption type. If selecting SSE-KMS, also enter the server-side encryption KMS key ID.

  9. Click Connect or Add.

Azure Blob storage Commercial

Setting Required Value
Name your drive Required A name for the connected drive.
Description Optional A description of the connected drive or any relevant details.
Container name Required The name of your Azure Blob Storage container.
Auth method Required The authentication method to use when connecting to your storage. Available options are connection string and service principal.
Connection string Visible and required if Auth method is set to Connection string. The connection string for your Azure storage account.
Service URL Visible and required if Auth method is set to Service principal. The endpoint for the Blob Service registered to the container’s storage account, such as https://.blob.core.windows.net/
Tenant ID Visible and required if Auth method is set to Service principal. The tenant ID for the service principal.
Client ID Visible and required if Auth method is set to Service principal. The client ID for the service principal.
Client secret Visible and required if Auth method is set to Service principal. The client secret for the service principal.

To connect Azure Blob storage:

  1. In the drive selection modal, select Azure Blob Storage.

  2. Enter a name for your drive and, optionally, a description.

  3. Enter your container name.

  4. Select an auth method.

    1. If the selected auth method is connection string, enter the connection string.

    2. If the selected auth method is service principal, enter the service URL, tenant ID, client ID, and client secret.

  5. Click Connect or Add.

Default drives Commercial

A default drive is the drive where all processed files for projects, conversations, and app runs in a workspace are stored by default. Default drives can be assigned at the organization level or the workspace level. The organization-level default drive applies to all workspaces in the organization, unless the workspace has a previously assigned workspace-level default drive. If a workspace has a default drive assigned at the workspace level, this overrides any changes to the organization-level default drive.

All workspaces and organizations, by default, have Instabase Drive as the default drive. Instabase Drive is the one terabyte of storage provided to all registered AI Hub accounts and organizations. The Instabase Drive can’t be removed, but you can change the default drive to another connected drive.

Changing the default drive impacts conversations and Build projects in all affected workspaces. Files stored on the previous default drive are not automatically migrated to the new default drive. In practice, this means that when the default drive changes for a workspace:

  • Any Build projects in the workspace must be deleted or migrated to the new default drive. When users open an affected Build project, they see a modal that can’t be dismissed. To continue working with the project, users must migrate the project.

  • Any existing conversations in the workspace become limited to previously uploaded files. Users can continue to view their conversation history and converse with any files already added to the conversation. To upload new files, users must create a new conversation.

Assigning default drives

Note

Only organization admins can assign default drives.

To assign an organization default drive:

Info

A drive must be connected at the organization level to be an organization default drive.

  1. From the Settings page, select the Drives tab.

  2. On the drive’s card, click the Settings (gear) icon.

  3. Select Make default drive.

  4. Click Set as default drive.

To assign a workspace default drive:

  1. From the My Hub tab, select the workspace.

  2. Under Drives, locate the drive’s card and click the Settings (gear) icon.

  3. Select Set as default drive.

  4. Click Set as default drive.

Removing connected drives

If you no longer want users to be able access a drive you previously mounted, you can remove it. There are some limitations to understand when removing drives:

  • Removing a drive completely disconnects the drive from AI Hub. Any processed AI Hub files stored on the drive are not deleted, but AI Hub loses the ability to reference those files in the future. Processed AI Hub files include Build project files, Converse conversation files, and app run results.

  • While you can later add a previously removed drive, doing so doesn’t restore the ability to reference any AI Hub files previously saved to the drive. If you want to reference AI Hub files previously saved to the drive, you must manually reupload them.

  • Default drives can’t be removed. To remove a default drive you must first assign another drive as the default.

  • The Instabase Drive can’t be removed. You can disable the Instabase Drive but not completely remove it.

To remove an organization drive:

  1. From the Settings page, select the Drives tab.

  2. On the drive’s card, click the Settings (gear) icon.

  3. Select Remove.

  4. Click Remove to confirm.

To remove a workspace drive:

  1. From the My Hub tab, select the workspace.

  2. Under Drives, locate the drive’s card and click the Settings (gear) icon.

  3. Select Remove.

  4. Click Disconnect to confirm.

Disable Instabase Drive

Instabase Drive is the default, organization-level storage provided to all AI Hub organizations. After connecting another drive, you can disable the Instabase Drive to hide it from members’ view. The same limitations apply as when removing a drive.

To disable Instabase Drive:

  1. From the Settings page, select the Drives tab.

  2. On the Instabase Drive’s card, click the Settings (gear) icon.

  3. Select Disable.

  4. Click Disable to confirm.