Skip to main content

What is Enscribe?

Enscribe is a team workspace for managing ENS-backed identity.

It gives an organization one place to manage a namespace, add contracts and wallets, create subnames, update ENS records, and track what changed.

How Enscribe is organized​

Enscribe is built around two core concepts:

  • An organization is your team workspace.
  • A namespace is one ENS name managed inside that workspace.

Each namespace has its own inventory, name management view, activity feed, settings, and API keys.

What teams use Enscribe for​

Teams use Enscribe to:

  • import an ENS name into a shared workspace,
  • add contracts, wallets, and Safe wallets to that namespace,
  • create subnames under the namespace,
  • update text records, address records, and content hashes,
  • stage several changes before submitting them onchain, and
  • review pending, completed, and failed operations from one activity log.

Why Enscribe exists​

Managing ENS directly across separate tools can be hard to coordinate when several people share responsibility for the same namespace.

One person may control the name, another may need to update records, and a third may need to review what happened later. If that work is spread across wallets, block explorers, and ad hoc notes, mistakes are easier to make and history is harder to follow.

Enscribe puts that workflow into one system. It adds shared organization access, namespace-level permissions, staged changes, and a clear record of operations.

How Enscribe handles namespace control​

When a team onboards a namespace, Enscribe helps transfer management to a supported control model.

Today, teams can choose:

  • Safe Multisig, when several signers should approve writes, or
  • Enscribe, when the team wants a direct managed setup.

This makes it possible to run ENS updates as a team workflow instead of a single-wallet workflow.

Beyond manual editing​

Enscribe is not only a UI for clicking through record changes.

Organizations and namespaces can also have API keys, which makes Enscribe useful for deployment pipelines, internal tools, and other systems that need programmatic access to namespace operations.

Next concept​

Continue to Naming smart contracts.