[ARVADOS] created: 2.1.0-1618-g39ce50e47

[Git user]

        at  39ce50e472535737446a54b2187ab4b38727a79c (commit)


commit 39ce50e472535737446a54b2187ab4b38727a79c
Author: Lucas Di Pentima <lucas.dipentima at curii.com>
Date:   Tue Nov 16 14:22:56 2021 -0300

    18363: Adds missing use case for protected property.
    
    Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <lucas.dipentima at curii.com>

diff --git a/doc/admin/collection-managed-properties.html.textile.liquid b/doc/admin/collection-managed-properties.html.textile.liquid
index 395200126..89aa18064 100644
--- a/doc/admin/collection-managed-properties.html.textile.liquid
+++ b/doc/admin/collection-managed-properties.html.textile.liquid
@@ -41,13 +41,23 @@ h4. Protected properties
 
 If there's a need to prevent a non-admin user from modifying a specific property, even by its owner, the @Protected@ attribute can be set to @true@, like so:
 
+<pre>
+Collections:
+  ManagedProperties:
+    sample_id: {Protected: true}
+</pre>
+
+This configuration won't assign a @sample_id@ property on collection creation, but if the user adds it to any collection, its value is protected from that point on.
+
+Another use case would be to protect properties that were automatically assigned by the system:
+
 <pre>
 Collections:
   ManagedProperties:
     responsible_person_uuid: {Function: original_owner, Protected: true}
 </pre>
 
-This property can be applied to any of the defined managed properties. If missing, it's assumed as being @false@ by default.
+If missing, the @Propected@ attribute it’s assumed as being @false@ by default.
 
 h3. Supporting example scripts
 

-----------------------------------------------------------------------


hooks/post-receive
--