text: <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>Administrator type</td><td>Administrative tasks</td></tr></thead><tbody><tr><td>System administrator</td><td>Creates a report administrator with Create Application Groups and Create Folders authority. Creates a user administrator with Create Groups authority. Creates and maintains storage sets. Creates and maintains system printers.</td></tr><tr><td>Report administrator</td><td>Creates and maintains application groups. Creates and maintains applications. Creates and maintains folders. Creates and maintains cabinets.</td></tr><tr><td>User administrator</td><td>Creates and maintains users. Creates and maintains groups.</td></tr></tbody>
          </table> </body> </html>
  
  To illustrate how the object owner model can be used, assume that a company installs a 
  Content Manager OnDemand system to provide data archival and retrieval services for other 
  organizations. The company provides the hardware and software that are required to 
  administer the system and archive and retrieve the data. An administrator from each 
  organization defines application groups and folders for their data. Another administrator 
  defines the users that can access the data. The system must be able to limit access to an 
  organization’s application groups and folders. Only users that are defined by an organization 
  must have access to the application groups and folders that are owned by the organization. 
  The system must also be able to limit access to the data. Only users that are defined by an 
  organization must have access to the data that is owned by the organization. 