Support

WOTT support is available for questions and issues related to your workspace, projects, notebooks, files, search, authentication, AI integrations, and remote MCP connections.

This support page provides guidance for common account, project, notebook, storage, search, and integration issues. If you cannot resolve an issue using the information below, contact the support team using the contact information provided at the end of this page.

When contacting support, provide enough information for us to understand and reproduce the issue. Do not include passwords, authentication tokens, private keys, API secrets, or other sensitive credentials in a support request.

To get started with WOTT, sign in to your account and create or open a project. Projects provide the primary workspace for organizing notebooks and other project content.

Inside a project, you can create notebooks and folders, organize content, edit Markdown-based notebook content, and search project knowledge.

Some features may require the appropriate project membership or permissions. If an action is unavailable, verify that you are signed in to the correct account and that you have access to the relevant project.

Projects are used to organize related notebooks, files, folders, and other project information. You can create projects, view projects you can access, and update supported project information.

Project access is controlled by project ownership, membership, visibility, and applicable permissions. You may only perform operations that your account is authorized to perform.

If a project does not appear in your project list, first verify that you are signed in to the correct account. If the project was shared with you, confirm that your membership or access has not been removed.

Project updates may be restricted to project owners or other authorized roles depending on the operation.

Notebooks contain your written project knowledge and can be organized directly inside a project or within folders.

Folders help organize notebooks and other supported notebook items. A notebook can be moved between supported locations when the account has permission to make that change.

If a notebook or folder is missing, check the project and parent folder you are viewing. Also verify that you are using the correct account and that the item has not been deleted.

Notebook and folder operations are subject to project access permissions.

Notebook content is stored as Markdown content. You can create notebooks, update their names and content, change supported metadata, and organize them within a project.

When updating a notebook, make sure the notebook identifier refers to the intended notebook and that you have permission to modify it.

If a content update does not appear immediately, refresh the notebook and verify that you are viewing the same project and notebook. If the problem continues, contact support with the notebook identifier and a description of the expected and actual result.

Avoid including passwords, API keys, access tokens, private keys, or other credentials in notebook content or support requests unless the information is specifically intended to be stored there and you understand the associated risks.

Project search helps you find relevant notebook content within a specific project. Search results are scoped to the project you specify and to content that your account is authorized to access.

Search is intended for finding information already stored in your project. It does not perform general web searches or automatically search other projects.

If search results are incomplete, try using more specific terms from the notebook content, alternative keywords, or a shorter query.

Search results may depend on indexed content. Newly created or updated content may require processing before all changes become available through search.

WOTT can be connected to supported AI clients through a remote MCP connection. When connected, the AI client can use the tools exposed by WOTT according to the permissions granted to your authenticated account.

During an authenticated connection, the integration may receive information required to identify your account and authorize requests. Tool calls may include project identifiers, notebook identifiers, search queries, notebook content, project information, or other data required to perform the requested operation.

The AI client determines when to invoke an available tool based on the conversation and the tool descriptions. Tool access does not grant access beyond the permissions associated with your authenticated account.

If a ChatGPT connection fails, verify that the MCP server URL is correct, authentication completed successfully, and the connection has not expired or been revoked.

WOTT can also be connected to supported Claude experiences through a remote MCP connection.

After authentication, Claude can invoke the tools exposed by WOTT within the permissions associated with your account. Available operations may include reading projects, managing notebooks, updating supported content, deleting notebooks, and searching project knowledge.

If the connection is unavailable, verify that the connector is enabled, the remote MCP endpoint is reachable, and authentication has completed successfully.

Disconnecting the connector prevents future tool calls from that connection, but it does not automatically delete your WOTT account or project data.

The remote MCP service exposes tools that allow compatible AI clients to interact with authorized WOTT workspace data.

Supported operations include listing projects, creating and updating projects, reading notebooks, creating and updating notebooks, deleting notebooks, and searching notebook content within a project.

Tool availability does not bypass normal authorization. Every operation is performed in the context of the authenticated user and is subject to the access rules of the relevant project.

Some operations modify or permanently delete data. AI clients should only perform these operations when the user's request clearly authorizes the action.

Remote MCP connections use an authentication flow to establish an authorized connection between your AI client and WOTT.

If authentication fails, first make sure you are signed in to the correct WOTT account and that the authorization flow completed successfully.

If you receive an authorization, token, or connection error, disconnect and reconnect the integration. This can resolve expired or invalid authorization state.

Do not share authorization codes, access tokens, refresh tokens, client secrets, private keys, or other authentication credentials with support or other users.

If repeated authentication failures continue, provide the exact error message, approximate time of the failure, the AI client you were using, and whether the issue occurs consistently.

Access to projects and notebooks depends on your account and the permissions associated with the project.

A user may be able to view a project without having permission to perform every modification. Certain project management operations may require ownership or another authorized role.

If you receive a permission error, verify that you are signed in to the intended account and that the account has access to the relevant project.

Do not attempt to bypass access controls or use another user's credentials to access project content.

Notebook deletion may be permanent. Deleting a notebook or folder can also remove associated descendants and related stored content depending on the item being deleted.

Because deletion can be destructive, confirm the notebook or folder identifier before performing the operation.

If content was deleted accidentally, contact support as soon as possible and provide the relevant project and item information. Recovery may not be possible in every case.

Disconnecting an AI integration does not restore content that was previously deleted.

Projects may support different visibility and sharing configurations. The availability of a project or its content to other users depends on the configured visibility and access permissions.

Before making a project public or sharing it with other users, review the project content to ensure that it does not contain information you intend to keep private.

Public or shared content may be accessible to people other than the original owner depending on the project's configuration.

If you believe private content has become publicly accessible unintentionally, contact support promptly and include the relevant project information.

Notebook and file-related functionality may use application storage to persist content and associated metadata.

If a file or notebook cannot be opened, verify that the item still exists, that you have access to the project, and that the item has not been deleted or moved.

For content synchronization issues, refresh the application and verify that the latest version of the notebook is being displayed.

When reporting a storage or file issue, provide the project identifier, item or notebook identifier, file type if applicable, and a description of what you expected to happen.

For unexpected behavior, start by refreshing the application and repeating the operation. Confirm that you are signed in to the intended account and are working in the correct project.

If an operation fails, record the exact error message rather than relying on a paraphrase. This helps support identify whether the issue is related to authentication, permissions, validation, storage, or another service.

For browser-related problems, try clearing cached application data or testing the operation in another supported browser. If the problem only occurs in one browser, include that information in your support request.

If the problem occurs across multiple devices or browsers, provide the approximate time the issue started and whether other operations continue to work.

If an MCP connection cannot be established, first verify that the configured remote MCP server address is correct and publicly reachable.

If authentication succeeds but tool calls fail, verify that the connected account has access to the project or notebook being requested.

If one tool fails while other tools work, provide the tool name, input you supplied, and exact error message when contacting support. Do not include authentication credentials or private secrets.

If the AI client appears to select the wrong tool, make the request more explicit by identifying the project, notebook, or operation you want to perform.

Tool behavior may also depend on the AI client's own tool-selection and authorization handling. If the same request behaves differently between AI clients, include the client name and version when reporting the issue.

Your use of WOTT is subject to the applicable Privacy Policy and Terms of Service.

For information about data collection, use, sharing, retention, deletion, AI integrations, MCP connections, and your privacy choices, review the Privacy Policy.

If you want to request deletion of your account or personal information, contact support using the applicable account or privacy contact method described in the Privacy Policy.

When making a privacy request, provide enough information for us to identify and process the request, but do not send passwords, authentication tokens, private keys, or other unnecessary sensitive information.

If you believe your account has been compromised, immediately secure your account and disconnect integrations that you do not recognize or no longer trust.

If you discover a potential security vulnerability affecting WOTT, report it through the designated security contact rather than publicly disclosing the vulnerability before it can be investigated.

Security reports should include a clear description of the issue, affected functionality, steps required to reproduce it, and any relevant technical information that can help with investigation.

Never include live credentials, authentication tokens, private keys, or other secrets in a security report. If sensitive material is required for investigation, use the secure reporting process provided by the support or security team.

A useful support request should describe what you were trying to accomplish, what happened, and what you expected to happen instead.

Where applicable, include the project identifier, notebook or item identifier, tool name, AI client, browser, approximate time of the issue, and exact error message.

For reproducible problems, provide clear steps that lead to the issue. This allows the support team to investigate the problem more efficiently.

Do not include passwords, access tokens, OAuth authorization codes, API keys, private keys, payment credentials, or other secrets in your support request.

If you cannot resolve an issue using this support documentation, contact the WOTT support team through the support contact information provided on this website.

For account, project, notebook, storage, search, or MCP issues, include the relevant identifiers and exact error information when available.

For privacy-related requests, use the privacy contact information provided in the Privacy Policy. For security vulnerabilities, use the designated security contact when one is provided.

Support response times may vary depending on the type and complexity of the request. Security and account-access issues may require additional verification before support can take action.