Designing at the platform
What the platform's own views and workflows are, and who reads them.
At the platform
With the scope switcher on the platform, the EntityView tab designs the platform's views: a view of a platform entity in a platform domain. Every tenant that has the domain open reads the entity through that view in Explorer, and an import into the entity maps to the fields it shows. There is one view per domain and entity.
The A_EntityView tab narrows a platform view for a platform application (one a platform domain holds). A package that carries the application carries its A_EntityViews with it. The same narrow-only rule holds: an application view can hide a field or make it required or read-only, never loosen what the domain view decides.
The Workflows lens designs the platform's workflows on platform entities, with guards and effects; an effect runs a platform action. A package carries a platform workflow at its published version, with its states, transitions, guards, effects and the actions they run. Platform workflow versions are not yet stamped with a metadata revision (the platform's revisions come later); the version number is what the package locks.
Keep in mind There is one A_EntityView per application and EntityView across the platform and every tenant for now: if a tenant already narrows that view for the application, the platform's is refused, and the refusal says so. A workflow key is unique per entity across the platform and every tenant.