A Command Center corresponds to a project in the underlying platform. It groups missions, tables, variables and app connections.

​
Select the workspace

Choose the workspace before creating a mission or connecting an account. Inspect its name and the accounts available to it. Existing mission configurations can still contain explicit external resource identifiers.

​
Additional Command Centers

Sydekyks 1.0.4 supports unlimited additional creator-owned Command Centers. Create one with + in the sidebar or Platform Admin → Command Centers → New Command Center. Select the intended center before adding missions and connected accounts. Additional centers support name and icon editing, with archive available when active work has stopped. Personal remains protected. Member sharing, custom roles, quotas and provisioning are not included in this lifecycle feature. Creating another center does not grant other users access. A dedicated deployment per customer can provide an operational boundary when that is the delivery design. See your workspace. Folders organize work. They do not establish a tenant or permissions boundary. Use the actual authentication and deployment controls required for the intended users.

​
Keep ownership clear

Record who maintains each enabled mission, which app account it uses and who decides when it changes. Store recovery procedures and provider-account ownership with the deployment operations record. When moving a mission through an export, reconnect accounts and validate resources in the destination. See import and export.