Skip to content
File Service

Fs Space

A space is a logical container for folders, files and objects, serving as a unit of horizontal scalability and a mechanism for isolating a group of resources. It can be thought of as a collection of these resources.

To create a space, you must specify a cloud provider and an accountId. The supported cloud providers are “aws” and “azure.” All resources within the space are organized and managed under the chosen provider. The accountId should be an IAM account identifier, though currently, no validation is performed against it. Space will be available only in the region in which they were created. Resources created in one region are not accessible from any other region.

Upon creation of a space, a root folder is automatically generated, which can be used to store and organize additional folders, files and objects within the space.

Spaces can have access control lists (ACLs) that define who can access the space and what operations they can perform. A space is always owned by its creator, who automatically receives the SpaceManager role’s permissions and can control the ACLs for the entire space.

Learn more about ACLs.

Storage Modes

Section titled “Storage Modes”

Spaces support different storage modes to control operations on resources

  • active: This mode permits all operations. This is the default mode.
  • read-only: In this restricted mode:
    • Space operations: Update, Delete, and Restore are permitted.
    • Folder operations: Only Export/Get is allowed. Create, Update, Rename, Move, Copy, Delete, and Restore are restricted.
    • File operations: Only Get operations are permitted. Upload, Update, Copy, Move, Rename, Lock/Unlock, Checkin/Checkout, Delete, Restore, and Link Support Files are restricted.

Users with spaceManager permission can update the storage mode using the update space endpoint.

Space Membership Boundary

Section titled “Space Membership Boundary”

Space membership boundary is a space-level setting that allows space managers to restrict sharing abilities such that only a select group of users is permitted to access content in the space. This feature provides the flexibility to:

  • Limit access to space content to members of a specified IAM group.
  • Share content with selected users outside the boundary.
  • Enable or disable the boundary at any time.

When a space membership boundary is declared, the following fields must be included:

  • Group: A group with the specified IAM group ID must be included. This defines the core membership for the space.

  • allowedRolesOutsideBoundary (Optional): A list of specific roles that can be assigned to users outside the specified IAM group. If provided, users outside boundary are strictly limited to using the roles defined in this list, while space members continue to use their standard ACL roles.

A space membership boundary can be configured in three ways:

  • No Membership Boundary (Default):
By default, there is no membership boundary. Any user can access the content based on standard ACL permissions.
  • Space Members Only:
To restrict access, set the group field. The allowedRolesOutsideBoundary field can be omitted. This prevents users outside the specified IAM group from having access.
  • Space Members with Limited Viewers:
This configuration grants access to space members based on their ACL roles, while allowing selected non-members to access the space using only a specific set of roles. This is achieved by setting the group field and defining the permitted roles in the allowedRolesOutsideBoundary list.

Space membership boundary is disabled by default, and can be set during space creation or updated later through the update space operation.

AI Processing

Section titled “AI Processing”

Spaces can be configured to allow or disallow AI-driven capabilities such as automated file summarization, vector indexing, and semantic search.

  • aiProcessingAllowed: A boolean flag indicating whether AI processing is permitted within the space. Defaults to true for newly created spaces. If set to false, requests to summarize or vectorize files within the space will be rejected.
  • Provider requirement: AI processing capabilities are supported only for spaces backed by AWS (provider: "aws").

Learn more about Summarization and Vectorization.

Note: Versioning does not apply to the space itself.