Platform / Commands

Turn intent
into an operation.

Commands give every workspace operation a direct path. Type /, search for what you need, and open the right operation without leaving the AI-first workspace.

The command model

A command is an explicit operation, not a magic phrase.

Each command describes a known operation, its target resource, and the workspace surface that should handle it. Selecting a command creates a manual tool call in the active conversation and can open the correct canvas for the next step.

01ChooseType / or open the Commands sidebar.
02FindSearch by command name, label, or resource.
03ContextSelect the table, record, field, or other target when required.
04OperateReview the operation in the workspace canvas.

Two surfaces

Use commands wherever work starts.

Prompt bar

Type / inside an active conversation to open the command menu. Search, use the arrow keys, press Enter, and the selected operation is added to that conversation.

Commands sidebar

Open the dedicated command surface to browse available operations, search the catalog, and select a command without first writing a prompt.

Keyboard flow: use Arrow Up and Arrow Down to move, Enter to select, and Escape to close the command menu.

Command families

A direct path to the work you repeat.

CreateBuild tables, fields, forms, actions, views, users, roles, approvals, and other workspace resources.
ListBrowse tables, actions, forms, views, approvals, users, roles, chatbots, and other available resources.
ViewOpen a specific table, record, field, form, action, view, role, user, or approval definition.
ResourcesOpen dashboards, reports, sheets, documents, presentations, scripts, pages, and skills.
OperationsOpen applications, Sandbox, permissions, email actions, notes, tasks, reminders, and chatbot management.
SystemReview application logs and inspect activity when an operation needs attention.

Dynamic table commands

Commands adapt to the tables you can access.

Table commands are generated from the tables available to your organization and your current access. The command catalog grows with the workspace instead of requiring a fixed command for every table.

/create:customers
/list:customers
/view:customers
/preview:customers
/history:customers
/export:customers
/import:customers

The table name in these examples represents an accessible table in your workspace. If access changes, the related dynamic commands can also change.

Context-aware operations

Some commands ask for the right context first.

A command can guide you through dependent selections before opening the final operation. This keeps the action explicit when a workspace contains many tables, records, fields, forms, or actions.

Table → record

Choose a table, search for a record, then open the record form, preview, or history view.

Table → field

Choose the table and field before viewing or changing a field definition.

Table → form

Choose a table and one of its forms before opening the form configuration.

Table → action or view

Choose the table, then select the action or saved view that should open.

Data movement

Import, export, and review the history.

Move data

Use /import:{table} to bring records into a selected table or /export:{table} to create an export file.

Review what happened

Use import history and export history commands to inspect prior jobs, statuses, row counts, errors, and generated files.

Import and export files belong to the shared resource layer, so they can be managed with the same permission-aware storage used by the rest of the platform.

Read Drive documentation ↗

Personal command center

Pin the operations your team repeats.

Commands can be pinned at three levels so the most useful operations stay close to the work.

OrganizationMake a command visible as a shared shortcut for the organization.
PersonalKeep a command close for your own repeated work.
ConversationPin a command for one specific workflow or active chat.

Recently used commands and usage counts also help the command center rank familiar operations. Unpin a command when it is no longer useful.

Permissions

Every command respects workspace access.

Commands are shortcuts to authorized operations, not a way around authorization. The command center checks active organization membership and filters resource commands based on the tables and resources the user can access.

Command missing

The command may not be enabled for the current surface, or the related table or resource may not be accessible to the current user.

Operation rejected

A command can be visible while the final operation still requires a valid target, permission, active conversation, or provider context.

Everyday examples

Start with a direct operation.

  1. Create a table. Run /create:table, then define the table structure in the workspace canvas.
  2. Inspect records. Run /list:customers or /view:customers and choose the record you need.
  3. Move data. Run /export:customers or /import:customers for the selected table.
  4. Review activity. Run /logs when you need to inspect application activity and execution logs.
  5. Open a platform capability. Run /sandbox, /chat-bots, /applications, or /resource-permission.
Build with prompts ↗Build agents ↗Read Sandbox ↗