Skip to content

Visibility and sharing

Visibility controls who can access an entity. Changing it never changes the URL — the URL is stable for the life of the entity.

Mode Who can access
private Only the creator (and grid admins).
grid Grid members in the listed spaces (or everyone in the grid).
link Anyone with the URL. Optionally require sign-in or allow search discovery.

Instead of a single mode, set the inside and outside axes directly for finer-grained control:

Axis Values Meaning
inside private | spaces | grid Who in the grid is an audience.
outside none | link | public Reach beyond the grid — public is anyone, findable by search engines.
Terminal window
# sign-in link — reachable only via the URL, not browsable inside the grid
grid visibility set my-app --inside private --outside link --require-signin
# both: also browsable by grid members
grid visibility set my-app --inside grid --outside link --require-signin
Terminal window
grid visibility show my-app
grid visibility set my-app link
grid visibility set my-app --inside grid --outside public # search-engine discoverable
grid visibility set my-app private

Scope grid visibility to specific spaces:

Terminal window
grid visibility set my-app grid --space engineering --space design
grid visibility add-space my-app marketing
grid visibility remove-space my-app design
  1. Set visibility to link:

    Terminal window
    grid visibility set my-app link
  2. Get the URL:

    Terminal window
    grid open my-app --print
    # https://my-app.your-grid.cloudgrid.io
  3. Send it. With link visibility, no account is needed to open it.

The MCP tools grid_visibility and grid_share change visibility from a chat, and default their target to the thing you just published — so “make it private” needs no ids.