Project data and integrations
Data and Integrations tools are intended for compatible Web or general-purpose projects. They are not a universal toolbar for Native builds or design-only prototypes. Availability depends on project route, permission, configured providers, and plan.
Data panel tabs
The Data panel can expose Database, Auth, Storage, Secrets, and Push resources. Database is for supported project data and recovery operations; Auth configures application identity; Storage manages app files; Secrets holds protected configuration; Push manages push capability when supported. Resource state can be not configured, provisioning, ready, failed, or disabled. Read the selected environment and confirmation summary before applying a production database change or restoring data.
Database and application data
Open Data to inspect the database resources associated with the project. Confirm the environment before querying or changing data. Use the schema or migration workflow presented by the project and inspect destructive changes before applying them. Project source checkpoints are not a backup of database contents.
Authentication and storage services
When supported, configure application identity, user login, or object storage through its dedicated panel. Review callback URLs, allowed origins, requested scopes, and environment assignment. Keep provider secrets on the server side and test using non-production accounts before enabling a production connection.
Integrations
Open Integrations to browse or connect the providers available to the project. Read the authorization request and data scope. Connect only what the application needs and verify that the correct organization and project are selected. Disconnect unused providers and revoke their credentials at the provider.
The integration workspace can group Connectors, AI, Commerce, Automations, Skills, Knowledge, Web search, and MCP. These areas serve different purposes: external business-service connections, application AI, commerce providers, event or scheduled workflows, project skills, reusable knowledge, web research, and authorized MCP tools. Not every category is available to every route.
Secret handling and changes
Use the dedicated secret or environment control rather than putting values in source. Record whether a value is for preview or production. A newly connected service may require source changes, a preview restart, or a new deployment. After changing it, verify the actual user flow and check service logs without exposing secret values.