Skip to content
Tano docs
Log in
Features/Writing and organization

Plugins

Plugins can add commands, views, or object capabilities to a workspace. Open the plugins page from the top of the sidebar and review the purpose and permissions before using one.

Install and authorize

Review the description and source. To import a code plugin, choose Import plugin, load its package, and inspect the manifest. Check the version and requested permissions before installing.

Installation and authorization are separate steps. Code plugins require authorization for the current version before running. Review new versions before authorizing them. An integrity digest does not verify the publisher's identity.

Catalog and submissions

Choose the community catalog to inspect publishers, source links, versions, release notes and permissions. Online workspaces use the connected server's catalog. Owners install or update; members authorize execution on their own devices. The upgrade preview compares permissions, network origins and native capabilities. Withdrawn releases remain in history and cannot be newly installed.

Developers can open Plugin submissions in settings, create a publisher profile and submit a JSON package with a version-specific source URL, license and release notes. Only reviewed releases enter the public catalog. The same page shows review decisions and supports cancelling pending submissions or requesting withdrawal. Changes to published bytes require a new version.

Workspace rules and personal choices

A workspace can define plugin availability and shared settings. Online workspace owners manage these rules, and members use the specified version. Personal enablement and code authorization stay in the account's storage on the current device.

Return to the plugins page to manage enablement. Installing a plugin does not grant operations that workspace rules or your permissions do not allow.

Storage and availability

Browser demo changes stay in the current browser. Local workspaces continue to use ordinary Markdown files; online workspaces use the service for documents and package distribution. Built-in plugins and the reviewed community catalog are separate. A submission is not automatically published or installed into workspaces.

See the editor guide for editing and saving, and access control for workspace permissions.

OverviewGet startedQuickstartStart in the demo and create your first document.OverviewGet startedBrowser demoLearn what the browser demo can do and where its content is stored.OverviewFoundationsCore conceptsUnderstand Markdown content, workspaces, and file identity.OverviewHelpFrequently asked questionsAnswers about storage, sync, and accounts.FeaturesWriting and organizationEdit documentsWrite with blocks, tables, properties, and source tools.FeaturesWriting and organizationMarkdown and filesExplore math, diagrams, enhanced blocks, and source preservation.