files.com 1.1.792 → 1.1.794

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5a2756de299d258badfc5abf4a2557d7e78d992b01976dad367f279846b465b2
-  data.tar.gz: 493010a6ed9c71039343234e90e0274c334b416aeab5ced41153acb6f0cd546d
+  metadata.gz: 2b13b897dc28165d84d3736775184a54e5fabc23d80109a575e87f2945512598
+  data.tar.gz: 6882635f60763cf6c6348051946fc2e9afb3c1d1d0021455d82d987e43dceaf3
 SHA512:
-  metadata.gz: 53ad30dc35fc6e2e7b2db69962f6314b3d7ec61d72197fa103adfe5d273147ff0dc1ef3fead7d96afb71ac1680bb836e35788110c19a602db6b83a605f298266
-  data.tar.gz: 67fcea479c8e1c2c7b05f2c6ca487a72734e9d6db9a9c4c2678a5057346e9e2aa7b24f57d03d14471fa9284201fc9b004eb929d89c66f3915aa4167b915f9217
+  metadata.gz: e9bd784476603c454fe028c45e09a2ed5f25380e60cace4b9cae1c5fe33fb6faf7091881ca609d171416fe73d48f29ff1aae339975b289b321800f4c0bcbeaf5
+  data.tar.gz: 4af70dc19ba7ccf9d8035e4633d78ba2c10e52e4ba677e5b41b440bf1c20b502722483e42966d4d01b94b093c494453575158cc6b5c105bf4b1ea2a77025abbd

data/README.md

@@ -12,6 +12,8 @@ The content included here should be enough to get started, but please visit our
 
 ## Introduction
 
+For integration choices and credential scope, start with [SDKs & APIs](https://www.files.com/docs/clients-and-protocols/sdks-and-apis). [Scripts, APIs & Application Workflows](https://www.files.com/docs/automated-workflows/scripts-apis-and-application-workflows) explains how to coordinate Files.com operations with the work your application owns.
+
 The Files.com Ruby gem provides convenient access to all aspects of Files.com from applications written in the Ruby language.
 
 Files.com customers use our Ruby gem for directly working with files and folders as well as performing management tasks such as adding/removing users, onboarding counterparties, retrieving information about automations and more.
@@ -54,7 +56,7 @@ Files::Folder).
 
 The Files.com Support team provides official support for all of our official Files.com integration tools.
 
-To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/overview/requesting-support) or simply send an E-Mail to support@files.com.
+To initiate a support conversation, you can send an [Authenticated Support Request](https://www.files.com/docs/support-and-services/requesting-support) or simply send an E-Mail to support@files.com.
 
 ## Authentication
 
@@ -66,12 +68,10 @@ Authenticating with an API key is the recommended authentication method for most
 the method used in the examples on this site.
 
 To use an API Key, first generate an API key from the [web
-interface](https://www.files.com/docs/sdk-and-apis/api-keys) or [via the API or an
+interface](https://www.files.com/docs/security/authentication-and-credentials/api-keys) or [via the API or an
 SDK](https://developers.files.com/ruby/resources/developers/api-keys).
 
-Note that when using a user-specific API key, if the user is an administrator, you will have full
-access to the entire API. If the user is not an administrator, you will only be able to access files
-that user can access, and no access will be granted to site administration functions in the API.
+A user key follows its account's permissions, narrowed by the key's permission scope, Workspace, and any path restriction on file operations. It can perform administrative operations only when both the account and key permit them. [API Keys](https://www.files.com/docs/security/authentication-and-credentials/api-keys) explains credential scope and lifecycle; [Workspaces](https://developers.files.com/ruby/overview/workspaces) explains request context and delegated administration.
 
 ```ruby title="Example Request"
 Files.api_key = 'YOUR_API_KEY'
@@ -90,10 +90,7 @@ Don't forget to replace the placeholder, `YOUR_API_KEY`, with your actual API ke
 
 ### Authenticate with a Session
 
-You can also authenticate by creating a user session using the username and
-password of an active user. If the user is an administrator, the session will have full access to
-all capabilities of Files.com. Sessions created from regular user accounts will only be able to access files that
-user can access, and no access will be granted to site administration functions.
+Create a session with the username and password of an active user. The session uses that user's permissions, including any delegated administrative access. [Workspaces](https://developers.files.com/ruby/overview/workspaces) describes account scope and administrative access.
 
 Sessions use the exact same session timeout settings as web interface sessions. When a
 session times out, simply create a new session and resume where you left off. This process is not
@@ -366,7 +363,7 @@ This behavior applies across:
 - Folder and file lookup operations
 - Automations and workflows
 
-See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity)
 
 ### Slashes
 

data/_VERSION

@@ -1 +1 @@
-1.1.792
+1.1.794

data/docs/sso_strategy.md

@@ -88,8 +88,8 @@
 * `provision_group_inclusion` (string): Comma-separated list of group names for groups (with optional wildcards) that will be auto-provisioned.
 * `provision_group_required` (string): Comma or newline separated list of group names (with optional wildcards) to require membership for user provisioning.
 * `provision_email_signup_groups` (string): Comma-separated list of group names whose members will be created with email_signup authentication.
-* `provision_readonly_site_admin_groups` (string): Comma-separated list of group names whose members will be created as Read-Only Site Admins.
-* `provision_site_admin_groups` (string): Comma-separated list of group names whose members will be created as Site Admins.
+* `provision_readonly_site_admin_groups` (string): Comma-separated list of group names used to grant or remove Read-Only Site Admin access for users on this SSO provider. When this list is nonempty and a directory sync changes a user's group membership, membership in at least one listed group grants this access; membership in none removes it, including access granted manually. Directory syncs include SCIM requests from any provider on the site, LDAP syncs, and sign-ins that set the user's groups from the identity provider. Membership changes made any other way, including through the web app, API, SDKs, or CLI, do not affect administrator access.
+* `provision_site_admin_groups` (string): Comma-separated list of group names used to grant or remove Site Admin access for users on this SSO provider. When this list is nonempty and a directory sync changes a user's group membership, membership in at least one listed group grants this access; membership in none removes it, including access granted manually. Directory syncs include SCIM requests from any provider on the site, LDAP syncs, and sign-ins that set the user's groups from the identity provider. Membership changes made any other way, including through the web app, API, SDKs, or CLI, do not affect administrator access.
 * `provision_group_admin_groups` (string): Comma-separated list of group names whose members will be provisioned as Group Admins.
 * `provision_attachments_permission` (boolean): 
 * `provision_dav_permission` (boolean): Auto-provisioned users get WebDAV permission?

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

@@ -151,12 +151,12 @@ module Files
       @attributes[:provision_email_signup_groups]
     end
 
-    # string - Comma-separated list of group names whose members will be created as Read-Only Site Admins.
+    # string - Comma-separated list of group names used to grant or remove Read-Only Site Admin access for users on this SSO provider. When this list is nonempty and a directory sync changes a user's group membership, membership in at least one listed group grants this access; membership in none removes it, including access granted manually. Directory syncs include SCIM requests from any provider on the site, LDAP syncs, and sign-ins that set the user's groups from the identity provider. Membership changes made any other way, including through the web app, API, SDKs, or CLI, do not affect administrator access.
     def provision_readonly_site_admin_groups
       @attributes[:provision_readonly_site_admin_groups]
     end
 
-    # string - Comma-separated list of group names whose members will be created as Site Admins.
+    # string - Comma-separated list of group names used to grant or remove Site Admin access for users on this SSO provider. When this list is nonempty and a directory sync changes a user's group membership, membership in at least one listed group grants this access; membership in none removes it, including access granted manually. Directory syncs include SCIM requests from any provider on the site, LDAP syncs, and sign-ins that set the user's groups from the identity provider. Membership changes made any other way, including through the web app, API, SDKs, or CLI, do not affect administrator access.
     def provision_site_admin_groups
       @attributes[:provision_site_admin_groups]
     end

metadata

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