anchor.diff:  - my-admin-user
   groups:
   - my-admin-group
  -
  +----
  +====
  +
  +Then, run `oc create` passing the file to create it:
  +
  +====
  +----
   $ oc create -f scc_admin.yaml
   securitycontextconstraints/scc-admin
  +
   $ oc get scc
   NAME         PRIV      CAPS      HOSTDIR   SELINUX     RUNASUSER
   privileged   true      []        true      RunAsAny    RunAsAny
   restricted   false     []        false     MustRunAs   MustRunAsRange
   scc-admin    true      []        false     RunAsAny    RunAsAny
   ----
  +====
   
   [[deleting-security-context-constraints]]
   
   == Deleting Security Context Constraints
   
  -[options="nowrap"]
  -----
  -$ oc delete scc scc-admin
  -securitycontextconstraints/scc-admin
  -----
  -
  -NOTE: If you delete the default security context constraints they will not be regenerated upon
  -restart unless you delete all security context constraints.  If any constraint already exists
  -within the system, no generation will take place.
  +To delete an SCC:
  +
  +----
  +$ oc delete scc <scc_name>
  +----
  +
  +[NOTE]
  +====
  +If you delete the default SCCs, they will not be regenerated upon restart,
  +unless you delete all SCCs. If any constraint already exists within the system,
  +no regeneration will take place.
  +====
   
   [[updating-security-context-constraints]]
   
   == Updating Security Context Constraints
   
  -[options="nowrap"]
  -----
  -$ oc edit scc privileged
  +To update an existing SCC:
  +
  +----
  +$ oc edit scc <scc_name>
   ----
   
   [[how-do-i]]
   
   == How Do I?
  +
  +The following describe common scenarios and procedures using SCCs.
   
   [[grant-access-to-the-privileged-scc]]
   
  
positive.code: 
  == Overview
  You can manage
  link:../architecture/additional_concepts/authorization.html#security-context-constraints[security context constraints]
  in your instance via the `oc` command as a normal API objects.
  
  [[listing-security-context-constraints]]
  
  == Listing Security Context Constraints
  
  [options="nowrap"]
  ----
  $ oc get scc
  NAME         PRIV      CAPS      HOSTDIR   SELINUX     RUNASUSER
  privileged   true      []        true      RunAsAny    RunAsAny
  restricted   false     []        false     MustRunAs   MustRunAsRange
  ----
  
  [[creating-new-security-context-constraints]]
  
  == Creating New Security Context Constraints
  
  Creating a new SCC is accomplished with the `oc create` command.  First, define the SCC in a json
  or yaml file and then run `oc create` passing the file.
  
  [options="nowrap"]
  ----
  kind: SecurityContextConstraints
  apiVersion: v1
  
negative.code: 
  . Add the user or group to the *users* or *groups* field of the SCC.
  
  For example, to allow the *e2e-user* access to the *privileged* SCC, add their
  user:
  
  ====
  