management_commands
The core's in-chat admin command catalogue — every command, what it lets a creator do, and how a connector declares the subset its surface renders.
Creators run their business from the dashboard, and, on a platform that has a conversation with them, from inside the platform: Telegram's platform bot walks a creator through creating a project, linking a channel, building a plan or sending a broadcast. Those flows call the same core actions the dashboard calls; the core publishes them as a command catalogue (Subscriby\Connector\Enums\ManagementCommand) and each connector declares which commands its in-chat surface renders, in its own idiom.
"management_commands": [
"project_create", "project_settings", "project_delete", "portal_design", "installation_connect",
"resource_link", "resource_manage", "plan_create", "plan_manage", "payment_method_setup",
"coupon_create", "referral_program_manage", "partner_program", "copilot", "access_codes_generate", "broadcast", "support_reply", "pass_roster",
"recovery_relink", "recovery_standby", "recovery_replace_resource", "account_recovery_email", "set_alert_destination", "donate"
]The list is optional, and meaningful only with the management_surface capability. ManagementSurface::commands() must return exactly the same set (management.commands_match_manifest), and the marketplace and the dashboard's Connectors tab show the coverage against the full catalogue, so a creator knows before installing what they can do from the platform and what needs the dashboard.
The catalogue
| Command | Lets the creator… |
|---|---|
project_create | Create a project. |
project_settings | Change a project's name, handle, portal and support settings. |
project_delete | Delete a project. |
portal_design | Design the project's portal page: the tagline and social links, the presets, colour mode and colours, the type, the shape, the layout, the creator's wording, the perks, questions and about card, the second button and the footer links, the announcement bar, the video, gallery and quotes, the order and visibility of the sidebar's parts and the blocks, the featured plan, the coupon box, the header buttons, the social proof, the seat badges and the share networks, the search engine and social card switches, the four pixel IDs, the title suffix and the description, the default language and the languages offered, the draft, preview and publish loop. |
installation_connect | Connect, reconnect or disconnect the project's installation on this connector. |
manage_connectors | See the project's installations and their health, and browse the catalogue. |
resource_link | Link a place the installation administers as a gated resource. |
resource_manage | Rename, disable, re-link or remove resources. |
plan_create | Build a plan: price, cycle, resources, trial, passes. |
plan_manage | Edit, publish, unpublish or delete plans. |
payment_method_setup | Connect a payment method (a gateway account, a native provider) to the project. |
coupon_create | Create a coupon. |
referral_program_manage | Set up, change, pause, resume or delete the Referral Program; approve, suspend, enrol and pay its affiliates. |
partner_program | Show a creator their Partner Program standing, referrals, commissions, payouts and commitments; take proof and a commitment added later; record how they are paid. |
copilot | Open Subscriby Copilot in the conversation: ask about the business, have the routine work done, confirm what changes something (Core\Copilot). |
access_codes_generate | Generate access codes for a plan. |
broadcast | Send a message to the project's members. |
support_reply | Answer a member's support conversation. |
support_relay_setup | Choose where support conversations are relayed and link the relay space. |
creator_tasks | See and complete the tasks creator_task grants opened. |
pass_roster | Read the Pass Roster one date at a time: the plans that sell dates, a plan's coming dates with their roll call, who holds a date and where each stands, and a holder's trail of moves (Core\PassRoster). |
recovery_status | See the Disaster Recovery Program's readiness, incidents and operations. |
recovery_relink | Prove a new account after losing the old one. |
recovery_standby | Register a standby installation, request a standby place, switch mirroring. |
recovery_replace_resource | Replace a lost place with a new one and re-admit its holders. |
account_recovery_email | Set or change the e-mail address account recovery uses. |
set_alert_destination | Route the creator's alerts to the account they are talking from, or stop (Core\Alerts). |
donate | Tip Subscriby. A connector extra (ManagementCommand::isConnectorExtra()): allowed, but not part of the catalogue's coverage. |
Every command names one or more core actions the connector drives through the Core API and the same authorisation the dashboard applies, so a teammate refused on the web is refused in the chat as well.
Declaring less
A connector need not render everything. The fake connector renders three (project_settings, plan_manage, resource_manage); a connector whose platform has no conversational UI (slash commands only, say) may render only the reads. What matters is that the manifest and commands() agree, and that every declared command has a real path through handle().
The Telegram list
Telegram declares the whole catalogue, the twenty-seven core commands and donate; Discord declares the twenty-seven core commands. The coverage line on each marketplace page reads full, and a command the core adds lands on both in the same release as its screens.
What the kit checks
management.commands_match_manifest: the sorted list ManagementSurface::commands() returns equals the sorted list the manifest declares. The loader refuses a value outside the catalogue and a duplicate.
How is this guide?
Last updated on
pacing
How fast the platform lets an installation send — the three intervals, the rate limiter the core registers from them, and which jobs read each value.
relay_modes
The support relay modes a connector offers — what a mode is, the two the core knows today, and how the manifest and the SupportRelay port must agree.