Skip to content
midlandDocs
Esc
navigateopen⌘Jpreview
On this page

Console

The admin surface that shows what the workspace holds, who is in it, what has happened and every entity's settings.

Console

The admin surface that shows what the workspace holds, who is in it, what has happened and every entity's settings.

The console is where admins govern the workspace. It is deliberately a small set of forms: the content lives in conversations with agents, and the console holds the rules around it.

Context

Every entity appears here, with its type, description, tags, owner and how much content it holds. Open one for its card: the current body or latest value, the entry index for a list, version history, and the settings below.

Manage entities

For each entity you set who can read, who can write, the two guides, tags, owner and update expectation, and you see the aliases agents have saved for it. The type is shown and cannot be changed.

Members

Members are people and couriers. You invite a person by email with an access level, describe each person so agents can name them, add a courier and set its reach, or remove a member.

Requests

Requests shows what the workspace was asked for and does not hold: the wording agents kept trying, with a count, beside the asks members wrote out in their own words. You define one, discard it or assign it to another admin. This is how a workspace grows from real demand, and Requests covers the loop in full.

Log

The log records everything that has happened to the workspace’s context: writes, agent reads and refused writes, newest first, each naming who, what and which entity.

Setup guide

When you invite a new member, they receive an email with a link to a guided flow that walks them through creating an account and installing the connector in their AI tools.

Was this page helpful?