Who owns a workflow or an application view
The platform's workflow and a tenant's own on the same entity, and which one runs.
Who owns a workflow or an application view
A Workflow is the platform's or a tenant's. A tenant runs the platform's workflow on a platform entity until it publishes one of its own on that entity; its own then wins, and the flow board says whose workflow it shows. The records' progress (instances and history) is always the tenant's.
In a tenant, a Workflow and an A_EntityView belong to the tenant that defines them, and no other tenant sees them. The tenant can build them on what it reads from the platform: a Workflow on a platform entity, an A_EntityView of a platform view. That refers to the platform definition and does not change it; the platform entity and its view are still changed only at the platform. At the platform, an A_EntityView is the platform's (see below).
Every change is decided on the server for the tenant you are working in, never for a tenant the page sends. When a change is refused, the reason is shown under the control: for example that the version is already published, that a key is taken, or that the definition is not visible in this tenant.
Keep in mind A Workflow key is unique per entity, and there is one A_EntityView per application and EntityView. On a platform entity or view that other tenants also build on, the key or the application may already be taken by another tenant; the refusal says so. Choose another key, EntityView or application.