Skip to documentation
Ask the docs

OriginChainDB / Guides

Use the current console

Find your instance, connect a client, explore records and understand the controls available to your role.

Open your workspace

Sign in at app.originchaindb.com, choose an organization, and open an instance. Use the organization view for Instances, Integrations, Team, Usage, Billing, Organization Settings and Plugins. Items are shown according to your permissions. Inside an instance, the navigation follows the database you selected.

AreaUse it for
OverviewInstance status and the Connect dialog with the endpoint, tenant and available connection methods.
WorkbenchWrite and run queries; inspect results and errors.
Data ExplorerBrowse namespaces, tables, fields and records. Opening a table’s query is separate from expanding its fields.
Database ManagementInspect database objects and the operations available for them.
Access ControlReview database roles and policies.
ConfigurationReview the instance settings available to your role.
PlatformOpen operational workflows, including Data migration under Migrations and Embeddings on dedicated configurations.

Create an instance and connect

  1. Open Instances and choose New instance. Review the available configuration and its requirements before submitting.
  2. Follow the provisioning status. When the instance is ready, open Overview, then Connect.
  3. Use the connection method offered for that instance. Copy the endpoint and tenant from the console; the tenant ID and instance ID are different values.
  4. Store a new key or token securely before confirming “I have stored it”. These secrets are shown once.

For an application or database client, open Integrations, pick the instance, and search the tool groups. Each available tool has its own setup guidance. Keep application credentials on your server.

Read-only tables and unavailable actions

Data Explorer lists tables even when its record editor cannot safely edit them. Tables without a usable primary key, some composite-key tables and other unsupported editing cases open read-only with a reason. Roles also control which actions are available. Read the explanation shown for a disabled control.

Workbench and Data Explorer wait while a sleeping instance wakes. If an action remains unresponsive after its stated requirements are met, contact the team with the page, action and error message, excluding credentials and private data.

Manage access when a teammate leaves

Removing a member, or leaving an organization, revokes that member’s personal instance tokens across the organization’s instances. The Team page shows any revocations still awaiting confirmation and offers Check again and Retry. Organization API keys are not revoked by member removal; review shared keys separately.

Explore with sample data

The public demo workspace runs with sample data in your browser and cannot connect to real instances. Open sign-in from the demo to use your own workspace. Values entered in the demo are not carried into the real console.

Follow a video or find an answer

Videos reflect the interface when recorded. Check the current console for newer options, and use the console FAQ when a step needs explanation.

Assign access through Team

Team supports groups, custom roles, database-scoped grants, deny rules and access review. Add people to the appropriate group, select the databases their grant covers, and review effective access before relying on it. Organization permissions and database roles are separate: an invitation alone does not grant every database operation.

Open optional tools from Plugins

Open Plugins in the organization sidebar to find tools such as Vezual (Beta). Follow each plugin's availability and setup requirements. Preview or beta status does not imply that every integration is enabled for your instance.