Find answers. Keep moving.

Start by confirming your sign-in method, then follow the message shown on the page.

1. Make sure you are using the correct Datus Studio address. For private deployments, use the address provided by your team.
2. Use the sign-in method you registered with or your team assigned. For enterprise SSO, sign in through the appropriate identity provider.
3. Check your account details and the error message. Do not share passwords, verification codes, or session cookies in the community.
4. If you still cannot sign in, email contact@datus.ai with your sign-in method, the time of the problem, and a redacted screenshot.

You can email the team without signing in or opening the product feedback page.

Distinguish your personal identity from team resources to find the right place to work.

1. Your account is your sign-in identity. A workspace organizes team members, projects, and data services.
2. A project contains data development work, context, conversations, and artifacts, and connects to the data sources and models it needs.
3. Check that you are in the correct workspace. One account can participate in several workspaces.
4. If a workspace or project is missing, ask its owner to confirm that your current account has access.

Having an account does not automatically give you access to every team project.

Check the address, network, credentials, and permissions before trying again.

1. Check that the database type, host, port, database name, and selected adapter match.
2. Confirm that the environment running Datus can reach the database. Ask an administrator to check private networking, IP allowlists, TLS, and firewall rules.
3. Confirm that the connection account and credentials are valid and have the minimum permissions required for the task.
4. Record the failure time and message. Share the database type and redacted connection details with the team, without passwords.

A connection working on your computer does not necessarily mean that the Datus runtime can reach the same database.

Prepare connection details and an access scope to reduce back-and-forth during setup.

1. Identify the database type, instance, database, and schemas or datasets you need to connect.
2. Prepare a connection account for Datus and restrict its resources and operations to the actual task.
3. Confirm the network path, TLS requirements, and source addresses that need to be allowed.
4. Enter credentials in the product configuration interface, verify the connection, and associate it with the project that needs it.

Enter credentials in the product interface. Avoid sending them in email, screenshots, or public community channels.

Users choose their model provider and configuration in Datus Studio. Check both the project setup and the provider-side response.

1. Confirm that the project is associated with a model connection and that the selected model matches the task.
2. Check that the provider, model name, API endpoint, and credential configuration match.
3. Use the provider error message to check API key permissions, account balance, request limits, or service availability.
4. If the cause is still unclear, share the provider, model name, failure time, and redacted error message, or record the Trace ID.

Do not send API keys. Provider service or account restrictions need to be handled using the corresponding provider guidance.

Choose the provider you intend to use, then associate the corresponding connection with your project.

1. Create or select a model connection in the model management page in Studio.
2. Enter the model name, API endpoint, and credentials required by the provider. For compatible APIs, confirm the exact model identifier.
3. Confirm that the provider account has permission and sufficient balance to use that model.
4. Associate the model connection with the target project and select the model in the workbench.

Model connections can differ between projects. Check the configuration in the project where the problem occurred.

Check your account and workspace first, then confirm access to the target resource.

1. Confirm the account you are signed in with and the workspace you are using.
2. Distinguish workspace membership, project permissions, and access to individual artifacts.
3. Ask the project or resource owner to confirm that access is still valid and the resource has not been removed or changed.
4. When contacting the team, include the target page URL, the time of the problem, and the error message, without sign-in credentials.

Access depends on resource permissions. Product assistance and support troubleshooting do not replace authorization by the resource owner.

The owner of the workspace, project, or artifact should confirm resource access.

1. Identify the workspace, project, or artifact you need to access.
2. Provide the owner with the account identifier you actually use to sign in to Datus.
3. Describe the task so the owner can assign the appropriate access scope.
4. After access is granted, reopen the target page. If the problem remains, record the URL and error message.

You do not need to share another team member’s account or session to obtain project access.

Start by checking the link and the artifact’s access scope.

1. Confirm that the link is complete and points to the report or dashboard you want to view.
2. If sign-in is required, use an account that has been granted access.
3. Ask the artifact owner to confirm that it is published, remains available, and allows access for your account.
4. If you have access but content does not load, provide the time, page URL, and a redacted screenshot of the error.

External access to a report or dashboard depends on its publication and sharing permissions.

Confirm the published version and recipient permissions before sending the link.

1. Check the report, dashboard, or Chatbot content and the version you intend to share.
2. Confirm that the artifact has completed the required publication steps.
3. Check recipient accounts or public access settings to avoid sharing data beyond the intended scope.
4. Ask recipients to verify access with their own identity rather than the sender’s signed-in session.

Updating source content does not necessarily update the published version. Confirm the version that was actually published.

Identify your infrastructure, access domain, and required external services before deploying.

1. Start with the public deployment documentation and select a deployment approach suited to your infrastructure.
2. Prepare the database, storage, networking, and configuration required by the guide. Deployment administrators should manage sensitive credentials.
3. Validate essential paths, including sign-in, database connectivity, and model calls.
4. When asking for help, include the deployment version, failure time, and redacted logs. Use your team’s agreed channel for enterprise support.

Public deployment documentation: https://studio.datus.ai/deployment. Production operations should be performed by the responsible deployment administrator.

The CLI and editor extension have separate installation, configuration, and integration documentation.

1. Visit docs.datus.ai and use the quickstart and configuration guide for your installed version.
2. For CLI issues, record the installed version, command, and redacted error output.
3. For editor extension issues, also record the editor and extension versions.
4. For open-source issues, search the corresponding GitHub repository. Discuss private environment details by email instead of in public issues.

Studio, CLI, and editor extensions have different entry points. Specify which product you are using in your request.