Command / Push Calls / Legacy Push Calls page

Legacy Push Calls page¶

Recognize the distinct legacy destination that still displays a fixed Coming soon message.

At a glance¶

Route: /workspaces/{workspace_id}/coming-soon/push-calls.

Who can open this page: collection. The workspace must have enabled entitlement and an active, verified membership; ownership does not bypass verification. Sign in with Discord. Sidebar visibility is separate from endpoint permission. This documentation never submits workspace requests.

What you see¶

The legacy page prints the feature label and Coming soon. It has no call table, contribution form or creation control. The functional Push Calls page is the current Command sidebar destination.

Who fills in each field¶

Calculations¶

No derived values on this page.

Freshness and updates¶

The fixed message is rendered on page load. It is not a collection result or a progress indicator.

Actions and permissions¶

Who can perform each action / Who can take action: each actor below needs the exact grant and conditions, independently of page visibility. All writes retain workspace scoping; same-origin checks apply as listed.

There are no feature actions on this unimplemented screen. In Trapitan, use the current Command → Push Calls sidebar destination to reach the implemented page; the legacy canvas itself has no feature link or form.

States and edge cases¶

Coming soon describes only this legacy screen. It does not mean the current Push Calls workflow is unavailable. A direct legacy route still requires authorization; hidden navigation does not grant access.

Related pages¶

Push Calls, Overview.

Source references¶

Source reviewed: 2026-10-07