anchor.diff:  
   . 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
  +For example, to allow the *e2e-user* access to the *privileged* SCC, add their
   user:
   
   ====
  
positive.code: - my-admin-user
  groups:
  - my-admin-group
  
  $ 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.
  
  [[updating-security-context-constraints]]
  
  == Updating Security Context Constraints
  
  [options="nowrap"]
  ----
  $ oc edit scc privileged
  ----
  
  [[how-do-i]]
  
  == How Do I?
  
  [[grant-access-to-the-privileged-scc]]
  
  
negative.code: 
  == Overview
  You can manage
  link:../architecture/additional_concepts/authorization.html#security-context-constraints[security
  context constraints] (SCCs) in your instance as normal API
  link:../architecture/core_concepts/overview.html[objects] using
  link:../cli_reference/overview.html[the CLI].
  
  [NOTE]
  ====
  You must have
  link:../architecture/additional_concepts/authorization.html#roles[*cluster-admin*
  privileges] to manage SCCs.
  ====
  
  [[listing-security-context-constraints]]
  
  == Listing Security Context Constraints
  
  To get a current list of SCCs:
  
  ====
  ----
  $ 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
  
  To create a new SCC, first define the SCC in a JSON or YAML file:
  
  .Security Context Constraint Object Definition
  ====
  ----
  kind: SecurityContextConstraints
  apiVersion: v1
  