Adding copy-to-space section to saved objects docs (#45513) (#45575)

* adding copy-to-space blurb to saved objects docs * Apply suggestions from code review Co-Authored-By: gchaps <[email protected]> * apply code review suggestions * Update docs/management/managing-saved-objects.asciidoc Co-Authored-By: Lisa Cawley <[email protected]>
elastic · Sep 13, 2019 · e28bf7a · e28bf7a
1 parent db04d8d
commit e28bf7a
Showing 1 changed file with 14 additions and 1 deletion.
diff --git a/docs/management/managing-saved-objects.asciidoc b/docs/management/managing-saved-objects.asciidoc
@@ -9,6 +9,7 @@ To get started, go to *Management > {kib} > Saved Objects*. With this UI, you ca
 
 * <<managing-saved-objects-view, View&#44; edit&#44; and delete saved objects>>
 * <<managing-saved-objects-export-objects, Import and export saved objects>>
+* <<managing-saved-objects-copy-to-space, Copy saved objects to another {kib} space>>
 * <<managing-saved-objects-object-definition, Edit the object definition>>
 
 
@@ -58,6 +59,19 @@ You have two options for exporting saved objects.
 This action creates an NDJSON with all your saved objects.  By default, 
 the NDJSON includes related objects. Exported dashboards include their associated index patterns.
 
+[float]
+[role="xpack"]
+[[managing-saved-objects-copy-to-space]]
+=== [xpack]#Copy to other {kib} spaces#
+
+To copy a saved object to another space, click the actions icon image:images/actions_icon.png[Actions icon]
+and select *Copy to space*. From here, you can select the spaces in which to copy the object.
+You can also select whether to automatically overwrite any conflicts in the target spaces, or
+resolve them manually.
+
+WARNING: The copy operation automatically includes related objects. If you don't want this behavior,
+use the <<spaces-api-copy-saved-objects, copy saved objects to space API>> instead.
+
 
 [float]
 [[managing-saved-objects-object-definition]]
@@ -80,4 +94,3 @@ WARNING: Validation is not performed for object properties. Submitting an invali
 change will render the object unusable. A more failsafe approach is to use 
 *Discover*, *Visualize*, or *Dashboard* to create new objects instead of 
 directly editing an existing one.
-