files.com 1.1.776 → 1.1.777

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f3ab164ab21a32d6176ed0ec790bcc8f3a51550fcc897807b4f6fd1659ce652f
-  data.tar.gz: e95e649aaa0a06b10f5ed46ef5ec75d9f4489ba4d3d63ed77caed4d15c158f8c
+  metadata.gz: 41ee15aacfc59a928215ccdd55f993d875355de89907f76fc7082adbfb98f69a
+  data.tar.gz: 9a6125da5b2d327c7601239fc2aa561b4dd68422181c561ffc0dce3d9b546aeb
 SHA512:
-  metadata.gz: d1e8fc4e3d370b84af05d117ca01cd21f3b7666f634f702611117fba7db44c539812ceed799a293aa3745e5257c83847ae9c20260b5cbd99b98314cae84b3ead
-  data.tar.gz: 3b2ea8663239164d966481d460432211b5875cde298d535aaa9f199a93e41be971a7202357b69f22c8da05770b1f6ca445a6901e97bca31141965c433ae0dea9
+  metadata.gz: 84bd52644dc78033492013f56f220e0bdac93e0bea0b1dd60612396998572d23ddd532b65bd2ae998adf6a7525596f10c4fa665d060e8901c32ed4b885e5c145
+  data.tar.gz: 0d1277b2c7581f386e65bcaa1b8b2a3d4eb553f0ad0931f3dec5711b512d963ce641a104b470154b023e94565d5ac570e42d786b55e7fec73d1f55ab2687ebf9

data/_VERSION

@@ -1 +1 @@
-1.1.776
+1.1.777

data/docs/api_key.md

@@ -36,7 +36,7 @@
 * `aws_secret_key` (string): AWS Secret Key to use with AWS-compatible endpoints, such as our Inbound S3-compatible endpoint.
 * `last_use_at` (date-time): API Key last used - note this value is only updated once per 3 hour period, so the 'actual' time of last use may be up to 3 hours later than this timestamp.
 * `name` (string): Internal name for the API Key.  For your use.
-* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
 * `platform` (string): If this API key represents a Desktop app, what platform was it created on?
 * `site_id` (int64): Site ID
 * `site_name` (string): Site Name
@@ -116,7 +116,7 @@ Files::ApiKey.create(
 * `name` (string): Required - Internal name for the API Key.  For your use.
 * `aws_style_credentials` (boolean): If `true`, this API key will be usable with AWS-compatible endpoints, such as our Inbound S3-compatible endpoint.
 * `path` (string): Restricts the file and folder operations made with this key, meaning the files, folders, and file_actions endpoints, to the specified folder and its descendants, including copy and move destinations. For `GET /file_migrations/{id}`, a key with a path can read only migrations it started. Other endpoints do not apply the path restriction; use the `files_only` permission set to confine a key to file operations and their supporting lookups. Does not grant access beyond the owning user's permissions. Optional except for `office_integration` keys, which require a path the owning user can read.
-* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
 * `workspace_id` (int64): Workspace ID for this API Key. `0` means the default workspace.
 
 
@@ -136,7 +136,7 @@ Files::ApiKey.update_current(
 
 * `expires_at` (string): API Key expiration date
 * `name` (string): Internal name for the API Key.  For your use.
-* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+* `permission_set` (string): Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
 
 
 ---

data/docs/bundle.md

@@ -23,6 +23,7 @@
   "form_field_set": {
     "id": 1,
     "title": "Sample Form Title",
+    "require_complete_metadata_capture": false,
     "form_layout": [
       1,
       2,

data/docs/event_delivery_attempt.md

@@ -8,6 +8,7 @@
   "event_record_id": 1,
   "event_subscription_id": 1,
   "event_target_id": 1,
+  "activity_notification_batch_id": 1,
   "workspace_id": 1,
   "status": "example",
   "attempt_number": 1,
@@ -26,6 +27,7 @@
 * `event_record_id` (int64): Event Record ID
 * `event_subscription_id` (int64): Event Subscription ID
 * `event_target_id` (int64): Event Target ID
+* `activity_notification_batch_id` (int64): Shared summary ID when this event is delivered in a Slack or Teams subfolder summary. All events in a summary share its delivery outcome.
 * `workspace_id` (int64): Workspace ID. 0 means the default workspace or site-wide.
 * `status` (string): Delivery status.
 * `attempt_number` (int64): Number of delivery attempts made.

data/docs/event_target.md

@@ -24,7 +24,7 @@
 * `apply_to_all_workspaces` (boolean): If true, this default-workspace target can receive events from all workspaces.
 * `enabled` (boolean): Whether this Event Target can receive events.
 * `config` (object): Event Target configuration. Folder targets accept path and format (json or csv).
-* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
 * `created_at` (date-time): Event Target create date/time.
 * `updated_at` (date-time): Event Target update date/time.
 
@@ -81,7 +81,7 @@ Files::EventTarget.create(
 * `apply_to_all_workspaces` (boolean): If true, this default-workspace target can receive events from all workspaces.
 * `enabled` (boolean): Whether this Event Target can receive events.
 * `config` (object): Required - Event Target configuration. Folder targets accept path and format (json or csv).
-* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
 * `target_type` (string): Required - Event Target type.
 
 
@@ -108,7 +108,7 @@ Files::EventTarget.update(id,
 * `apply_to_all_workspaces` (boolean): If true, this default-workspace target can receive events from all workspaces.
 * `enabled` (boolean): Whether this Event Target can receive events.
 * `config` (object): Event Target configuration. Folder targets accept path and format (json or csv).
-* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
 
 
 ---
@@ -149,7 +149,7 @@ event_target.update(
 * `apply_to_all_workspaces` (boolean): If true, this default-workspace target can receive events from all workspaces.
 * `enabled` (boolean): Whether this Event Target can receive events.
 * `config` (object): Event Target configuration. Folder targets accept path and format (json or csv).
-* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+* `delivery_policy` (object): Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
 
 
 ---

data/docs/form_field_set.md

@@ -6,6 +6,7 @@
 {
   "id": 1,
   "title": "Sample Form Title",
+  "require_complete_metadata_capture": false,
   "form_layout": [
     1,
     2,
@@ -37,6 +38,7 @@
 
 * `id` (int64): Form field set id
 * `title` (string): Title to be displayed
+* `require_complete_metadata_capture` (boolean): Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
 * `form_layout` (array(int64)): Layout of the form
 * `form_fields` (array(object)): Associated form field definitions; authenticated form field set responses include historical definitions, while form_layout identifies current fields
 * `skip_name` (boolean): Any associated InboxRegistrations or BundleRegistrations can be saved without providing name
@@ -85,6 +87,7 @@ Files::FormFieldSet.find(id)
 Files::FormFieldSet.create(
   user_id: 1, 
   title: "Sample Form Title", 
+  require_complete_metadata_capture: false, 
   workspace_id: 1, 
   skip_email: false, 
   skip_name: false, 
@@ -97,6 +100,7 @@ Files::FormFieldSet.create(
 
 * `user_id` (int64): User ID.  Provide a value of `0` to operate the current session's user.
 * `title` (string): Title to be displayed
+* `require_complete_metadata_capture` (boolean): Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
 * `workspace_id` (int64): Workspace ID
 * `skip_email` (boolean): Skip validating form email
 * `skip_name` (boolean): Skip validating form name
@@ -111,6 +115,7 @@ Files::FormFieldSet.create(
 ```
 Files::FormFieldSet.update(id, 
   title: "Sample Form Title", 
+  require_complete_metadata_capture: false, 
   workspace_id: 1, 
   skip_email: false, 
   skip_name: false, 
@@ -123,6 +128,7 @@ Files::FormFieldSet.update(id,
 
 * `id` (int64): Required - Form Field Set ID.
 * `title` (string): Title to be displayed
+* `require_complete_metadata_capture` (boolean): Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
 * `workspace_id` (int64): Workspace ID
 * `skip_email` (boolean): Skip validating form email
 * `skip_name` (boolean): Skip validating form name
@@ -152,6 +158,7 @@ form_field_set = Files::FormFieldSet.find(id)
 
 form_field_set.update(
   title: "Sample Form Title",
+  require_complete_metadata_capture: false,
   workspace_id: 1,
   skip_email: false,
   skip_name: false,
@@ -164,6 +171,7 @@ form_field_set.update(
 
 * `id` (int64): Required - Form Field Set ID.
 * `title` (string): Title to be displayed
+* `require_complete_metadata_capture` (boolean): Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
 * `workspace_id` (int64): Workspace ID
 * `skip_email` (boolean): Skip validating form email
 * `skip_name` (boolean): Skip validating form name

data/docs/site.md

@@ -97,6 +97,7 @@
   "disable_all_ai_features": true,
   "disable_files_certificate_generation": true,
   "disable_notifications": true,
+  "file_activity_events_enabled": true,
   "disable_password_reset": true,
   "domain": "my-custom-domain.com",
   "domain_hsts_header": true,
@@ -447,6 +448,7 @@
 * `disable_all_ai_features` (boolean): If true, all AI features are disabled for this site.
 * `disable_files_certificate_generation` (boolean): If set, Files.com will not set the CAA records required to generate future SSL certificates for this domain.
 * `disable_notifications` (boolean): Are notifications disabled?
+* `file_activity_events_enabled` (boolean): If true, file operations produce file_action.activity.v1 EventChannel events in all workspaces. Defaults to false; subscription filters and workspace access still control delivery.
 * `disable_password_reset` (boolean): Is password reset disabled?
 * `domain` (string): Custom domain
 * `domain_hsts_header` (boolean): Send HSTS (HTTP Strict Transport Security) header when visitors access the site via a custom domain?
@@ -649,6 +651,7 @@ Files::Site.update(
   legacy_checksums_mode: false, 
   migrate_remote_server_sync_to_sync: false, 
   as2_message_retention_days: 1, 
+  file_activity_events_enabled: false, 
   username_display: "username_only", 
   session_expiry_minutes: 1, 
   ssl_required: false, 
@@ -837,6 +840,7 @@ Files::Site.update(
 * `legacy_checksums_mode` (boolean): Use legacy checksums mode?
 * `migrate_remote_server_sync_to_sync` (boolean): If true, we will migrate all remote server syncs to the new Sync model.
 * `as2_message_retention_days` (int64): Number of days to retain AS2 messages (incoming and outgoing).
+* `file_activity_events_enabled` (boolean): If true, file operations produce file_action.activity.v1 EventChannel events in all workspaces. Defaults to false; subscription filters and workspace access still control delivery.
 * `username_display` (string): How usernames are displayed in the web UI. Can be `username_only`, `full_name_only`, `full_name_username`, `full_name_company`, or `full_name_username_company`.
 * `session_expiry_minutes` (int64): Session expiry in minutes
 * `ssl_required` (boolean): Is SSL required?  Disabling this is insecure.

data/lib/files.com/models/api_key.rb

@@ -104,7 +104,7 @@ module Files
       @attributes[:name] = value
     end
 
-    # string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+    # string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
     def permission_set
       @attributes[:permission_set]
     end
@@ -295,7 +295,7 @@ module Files
     #   name (required) - string - Internal name for the API Key.  For your use.
     #   aws_style_credentials - boolean - If `true`, this API key will be usable with AWS-compatible endpoints, such as our Inbound S3-compatible endpoint.
     #   path - string - Restricts the file and folder operations made with this key, meaning the files, folders, and file_actions endpoints, to the specified folder and its descendants, including copy and move destinations. For `GET /file_migrations/{id}`, a key with a path can read only migrations it started. Other endpoints do not apply the path restriction; use the `files_only` permission set to confine a key to file operations and their supporting lookups. Does not grant access beyond the owning user's permissions. Optional except for `office_integration` keys, which require a path the owning user can read.
-    #   permission_set - string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+    #   permission_set - string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
     #   workspace_id - int64 - Workspace ID for this API Key. `0` means the default workspace.
     #
     # params:: Hash of API operation parameter values.
@@ -319,7 +319,7 @@ module Files
     # Parameters:
     #   expires_at - string - API Key expiration date
     #   name - string - Internal name for the API Key.  For your use.
-    #   permission_set - string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user, and every other endpoint denies them with `not-authorized/api-key-only-for-file-operations`.
+    #   permission_set - string - Permissions for this API Key. Keys with the `desktop_app` permission set only have the ability to do the functions provided in our Desktop App (File and Share Link operations). Keys with the `office_integration` permission set are auto generated, and automatically expire, to allow users to interact with office integration platforms. Keys with the `files_only` permission set can use only the files, folders, and file_actions endpoints, excluding the GPG Encrypt and GPG Decrypt file actions, where they perform file operations as a full-access file user in the key's workspace scope, along with `GET /file_migrations/{id}` and `GET /api_key`. On the migration lookup, any key with a `path` can read only migrations it started. Without a `path`, user-owned keys retain user-scoped access; site-wide Workspace-bound keys can read only migrations whose source and destination are both in their Workspace. Every `files_only` key is Workspace-bound, including Workspace `0`, as is a full-access key in a named Workspace. A full-access site-wide key in the default Workspace retains Site-wide migration access. Migrations outside the caller's visibility return `not-found`. Keys with `files_only` cannot use site admin, workspace admin, folder admin, group admin, partner admin, or billing privileges from the owning user. Both GPG file actions and every other endpoint deny them with `not-authorized/api-key-only-for-file-operations`. Folder-configured GPG encryption and decryption still apply to files uploaded with a `files_only` key.
     #
     # params:: Hash of API operation parameter values.
     # options:: Hash of optional request configuration passed to Files::Api.send_request.

data/lib/files.com/models/event_delivery_attempt.rb

@@ -29,6 +29,11 @@ module Files
       @attributes[:event_target_id]
     end
 
+    # int64 - Shared summary ID when this event is delivered in a Slack or Teams subfolder summary. All events in a summary share its delivery outcome.
+    def activity_notification_batch_id
+      @attributes[:activity_notification_batch_id]
+    end
+
     # int64 - Workspace ID. 0 means the default workspace or site-wide.
     def workspace_id
       @attributes[:workspace_id]

data/lib/files.com/models/event_target.rb

@@ -72,7 +72,7 @@ module Files
       @attributes[:config] = value
     end
 
-    # object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+    # object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
     def delivery_policy
       @attributes[:delivery_policy]
     end
@@ -97,7 +97,7 @@ module Files
     #   apply_to_all_workspaces - boolean - If true, this default-workspace target can receive events from all workspaces.
     #   enabled - boolean - Whether this Event Target can receive events.
     #   config - object - Event Target configuration. Folder targets accept path and format (json or csv).
-    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
     def update(params = {})
       params ||= {}
       params[:id] = @attributes[:id]
@@ -192,7 +192,7 @@ module Files
     #   apply_to_all_workspaces - boolean - If true, this default-workspace target can receive events from all workspaces.
     #   enabled - boolean - Whether this Event Target can receive events.
     #   config (required) - object - Event Target configuration. Folder targets accept path and format (json or csv).
-    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
     #   target_type (required) - string - Event Target type.
     #
     # params:: Hash of API operation parameter values.
@@ -219,7 +219,7 @@ module Files
     #   apply_to_all_workspaces - boolean - If true, this default-workspace target can receive events from all workspaces.
     #   enabled - boolean - Whether this Event Target can receive events.
     #   config - object - Event Target configuration. Folder targets accept path and format (json or csv).
-    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400.
+    #   delivery_policy - object - Event Target delivery policy. Email and folder targets support batch_interval in seconds, between 600 and 86400. Slack and Teams support delivery_mode (immediate or subfolder_summary), summary_path (empty string means root), and summary_delay (15–300 seconds, default 60). The summary applies to matching file activity under summary_path; other matching events retain immediate delivery.
     #
     # params:: Hash of API operation parameter values.
     # options:: Hash of optional request configuration passed to Files::Api.send_request.

data/lib/files.com/models/form_field_set.rb

@@ -27,6 +27,15 @@ module Files
       @attributes[:title] = value
     end
 
+    # boolean - Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
+    def require_complete_metadata_capture
+      @attributes[:require_complete_metadata_capture]
+    end
+
+    def require_complete_metadata_capture=(value)
+      @attributes[:require_complete_metadata_capture] = value
+    end
+
     # array(int64) - Layout of the form
     def form_layout
       @attributes[:form_layout]
@@ -101,6 +110,7 @@ module Files
 
     # Parameters:
     #   title - string - Title to be displayed
+    #   require_complete_metadata_capture - boolean - Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
     #   workspace_id - int64 - Workspace ID
     #   skip_email - boolean - Skip validating form email
     #   skip_name - boolean - Skip validating form name
@@ -196,6 +206,7 @@ module Files
     # Parameters:
     #   user_id - int64 - User ID.  Provide a value of `0` to operate the current session's user.
     #   title - string - Title to be displayed
+    #   require_complete_metadata_capture - boolean - Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
     #   workspace_id - int64 - Workspace ID
     #   skip_email - boolean - Skip validating form email
     #   skip_name - boolean - Skip validating form name
@@ -218,6 +229,7 @@ module Files
 
     # Parameters:
     #   title - string - Title to be displayed
+    #   require_complete_metadata_capture - boolean - Reject answers over 1024 characters or more than 32 answered custom fields to ensure complete file metadata capture
     #   workspace_id - int64 - Workspace ID
     #   skip_email - boolean - Skip validating form email
     #   skip_name - boolean - Skip validating form name

data/lib/files.com/models/site.rb

@@ -361,6 +361,11 @@ module Files
       @attributes[:disable_notifications]
     end
 
+    # boolean - If true, file operations produce file_action.activity.v1 EventChannel events in all workspaces. Defaults to false; subscription filters and workspace access still control delivery.
+    def file_activity_events_enabled
+      @attributes[:file_activity_events_enabled]
+    end
+
     # boolean - Is password reset disabled?
     def disable_password_reset
       @attributes[:disable_password_reset]
@@ -1076,6 +1081,7 @@ module Files
     #   legacy_checksums_mode - boolean - Use legacy checksums mode?
     #   migrate_remote_server_sync_to_sync - boolean - If true, we will migrate all remote server syncs to the new Sync model.
     #   as2_message_retention_days - int64 - Number of days to retain AS2 messages (incoming and outgoing).
+    #   file_activity_events_enabled - boolean - If true, file operations produce file_action.activity.v1 EventChannel events in all workspaces. Defaults to false; subscription filters and workspace access still control delivery.
     #   username_display - string - How usernames are displayed in the web UI. Can be `username_only`, `full_name_only`, `full_name_username`, `full_name_company`, or `full_name_username_company`.
     #   session_expiry_minutes - int64 - Session expiry in minutes
     #   ssl_required - boolean - Is SSL required?  Disabling this is insecure.

data/lib/files.com/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Files
-  VERSION = "1.1.776"
+  VERSION = "1.1.777"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: files.com
 version: !ruby/object:Gem::Version
-  version: 1.1.776
+  version: 1.1.777
 platform: ruby
 authors:
 - files.com
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-10-11 00:00:00.000000000 Z
+date: 2026-10-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: addressable