Datasite

Create filerooms, folders, or a folder hierarchy in a Datasite project.

• No parentId: Top-level entries become filerooms
• With parentId: Entries become folders under that parent

contentPaths is a flat JSON array where each entry is a full path string plus optional type and published flag:

• path (required): Full slash-separated path, e.g. "/Financial/Q1" or "/Legal"
• type (optional): Override type for the final segment of this path — FILEROOM or FOLDER (auto-inferred if omitted)
• published (optional): Whether the final segment of this path is visible to non-admin users (defaults to false). Not applicable in PREPARE projects — publishing is not supported.

Shared ancestor segments are deduplicated automatically. To set type or published (non-PREPARE only) on an ancestor, list it as its own entry alongside its children (e.g. {"path":"/Financial","type":"FILEROOM"} and {"path":"/Financial/Q1"}). Example: [{"path":"/Financial/Q1"},{"path":"/Financial/Q2"},{"path":"/Legal"}]

PREPARE projects use the Staging Folder (sandbox) exclusively. Do not create new filerooms or folders outside the sandbox on PREPARE projects — create content only within the Staging Folder. Do not suggest publishing content for PREPARE projects — publishing is not a supported feature in PREPARE.

Get access control information for a Datasite project. Supports three scopes:

• PROJECT: List all roles, and optionally the project's available feature accesses catalog
• PERMISSIONS: Show which roles can access a specific document or folder (requires metadataId)
• ROLE: Show details for a specific role including feature accesses (requires roleId)

Get members of a project or subscription. Returns user membership details including status and role. Use scope=PROJECT for project members or scope=SUBSCRIPTION for subscription members. Optionally provide a userId to get a single member's details.

Get a comprehensive overview of a Datasite project in a single call. Returns project details plus optional sections: role listing, member count, and Q&A summary. Use listFolderContents to explore the fileroom/folder hierarchy.

Get Q&A information for a Datasite project. Returns either:

• A specific question with all posts and answers (when questionId is provided)
• An overview with question listing, summary dashboard, and categories (when questionId is omitted)

Use manageQuestion for creating or updating questions.

Grant a role-level feature access permission in a Datasite project. This controls which roles can access specific project features (e.g. Q&A, bulk download) — it does not activate paid product features like AI-powered content search. Use getAccessControl(scope=PROJECT, includeFeatureAccesses=true) to discover available keys.

Invite a user to a Datasite project by email address and assign them a role. You can specify the role by name (e.g., "Reviewer") or by ID. When using roleName, the server resolves it to the correct role ID automatically. Role names are resolved to IDs automatically.

List the contents of filerooms and folders in a Datasite project. Returns item metadata — names, IDs, types (FILEROOM, FOLDER, DOCUMENT, PLACEHOLDER, SANDBOX), statuses, file types, and publishing states — but NOT document text. Use this to navigate the folder tree, see what documents exist and their metadata, or find where content is located before creating, uploading, or modifying it. To find information inside documents (e.g. clauses, risks, or specific content), use searchDocuments instead.

Behavior by parameters:

• No metadataId: Returns the top-level fileroom listing with IDs.
• With metadataId: Returns the direct children of that folder or fileroom.
• depth (default 1, max 10): Controls how many levels deep to traverse. depth=1 returns immediate children only. depth > 1 performs a BFS traversal of the folder hierarchy, returning all items with depth and path columns so you can understand the full structure in one call instead of browsing level by level.
• foldersOnly (default true): When true, only folder-type items (FILEROOM, FOLDER, SANDBOX, INBOX) are returned. Set to false to include documents in the results. Applies at all depth levels.

The listing may include items with type SANDBOX (named "Staging Folder"). A sandbox is a staging area where content is uploaded before being published to regular filerooms. PREPARE projects use the sandbox exclusively for uploads — all content must go through the Staging Folder.

List all Datasite projects you have access to, optionally enriched with subscription context. Use this to find projects by name, state, or to discover which subscription a project belongs to. Set includeSubscriptionInfo=true to include subscription details.

List all Datasite subscriptions you have access to. Returns subscription name, ID, and allowed offering types. Use this to find which subscription to use when creating a new project.

Create, update, or categorize Q&A questions in a Datasite project. action=CREATE: requires categoryId (use getQAStatus with includeCategories=true to list categories). action=UPDATE: requires questionId. Supports closing/reopening via the closed param. action=CREATE_CATEGORY: requires categoryName.

Create or update a role in a Datasite project. action=CREATE: requires name. action=UPDATE: requires roleId, optional name to rename.

Search across document content in a Datasite project using AI-powered semantic search with reranking. Returns matching text passages from inside documents with relevance scores, page numbers, and source paths. Use this whenever you need to find information, clauses, risks, or answers within documents — not for navigating folder structure. If the feature is not enabled on the project, this tool returns guidance to contact Datasite — always attempt the search rather than skipping it.

Create a new Datasite project and optionally set up its initial content structure in one call.

IMPORTANT: Before calling this tool, always call listSubscriptions first. If the user has any subscriptions, you MUST ask them to choose one and pass its ID as subscriptionId. Do not call this tool without a subscriptionId unless listSubscriptions returned an empty list.

A Staging Folder (sandbox) is automatically created for the project. If contentPaths is provided, paths default to folders inside the sandbox unless an explicit type override is provided.

contentPaths is a flat JSON array where each entry is a full path string plus optional type and published flag:

• path (required): Full slash-separated path, e.g. "/Financial/Q1" or "/Legal"
• type (optional): Override type for the final segment of this path — FILEROOM or FOLDER (auto-inferred if omitted)
• published (optional): Whether the final segment of this path is visible to non-admin users (defaults to false). Not applicable in PREPARE projects — publishing is not supported.

Shared ancestor segments are deduplicated automatically. To set type on an ancestor, list it as its own entry alongside its children (e.g. {"path":"/Financial","type":"FILEROOM"} and {"path":"/Financial/Q1"}). Example: [{"path":"/Financial/Q1"},{"path":"/Financial/Q2"},{"path":"/Legal"}]

Do not suggest publishing content for PREPARE projects — publishing is not a supported feature in PREPARE.

Update a document or folder in a Datasite project. Supports renaming, and supports changing publishing status only for non-PREPARE projects. Identify the item by metadataId or human-readable path (e.g., "Financial/Q1 Reports"). Do not suggest publishing status changes for PREPARE projects — publishing is not a supported feature in PREPARE.

Activate or deactivate a user's membership in a Datasite project. Use getMembers to find user IDs. Status must be ACTIVATED or DEACTIVATED.

Get a link to manage content permissions for a Datasite project via the web application. Optionally provide a fileroom or folder ID to navigate directly to its permissions page. Returns a browser URL where the user can review and update permissions manually.

Get a link to upload documents to a Datasite project via the web application. Specify the destination as a human-readable path (e.g., "Financial/Q1 Reports") or a direct folder ID. Returns a browser URL that opens the target folder in the Datasite web application, where the user can complete the upload.

For PREPARE projects, uploads must target the Staging Folder (sandbox). Browse content first to find the sandbox, then use its path or ID as the destination.