On this page


Use the page edit pattern when you want users to manage a service resource by editing its properties and configuration in bulk.
Use inline edit on views where information needs to be updated often, or when you want a user to edit a resource property across multiple resources.


Page editInline edit
Use-caseEditing multiple properties of one resourceEditing one property across multiple resources
Dependency between the propertiesSettings are interdependentSettings are independent
ContextEditing in a dedicated pageEditing in context


Depending on the use case, one interaction model can be more effective than the other. Page edit is preferred when editing multiple properties or configurations of one resource, while inline edit is preferred when editing one property or configuration across multiple resources.

Dependency between the properties

Page edit provides a more effective way to explain the relationships between resources properties, for example, when editing happens within a multi page creation flow, or when properties are related. 


The context in which the editing is performed can set up your users for success. Editing multiple properties or configurations of one resource within a standalone page supports the the user mental model of being in an edit mode. 
Performing inline edits to multiple resources within a set of resources, for example a table view, is preferred to keep users within the context of the parameters displayed.