á
á

Appendix E - User administration
In a SuperOffice installation on a SQL server, the user term is used in two different ways. First you have the internal SuperOffice user used internally in SuperOffice to define the users diary etc. Secondly you have the database user account inside the SQL database. This user gives access to the data stored in the database. In a SQL installation of SuperOffice these two users have to be the same. This means they must have the same userid and password inside SuperOffice and inside the SQL database.

In SQL Server the database user accounts and login accounts are managed separately. A new login account can be created only by the system administrator (SA). A new login account must be present before a new user can be added to the SuperOffice database in SQL Server.

There are two strategies you can choose to administer users for SuperOffice on MS SQL server.

Split managing of users into to steps
This is done by managing SuperOffice users (login name and password in the SuperOffice application), and managing logins and users in your SQL database separately. This method is recommended if you have other databases running on your SQL Server, and the users are using the same logins as in SuperOffice. In this way the DBA will have complete control of all logins from within the SQL Server, and nobody can lock other users out from other application by changing their userid or password from with inside SuperOffice.

How to manage users in this way is described below in E.1

Managing both SuperOffice and SQL Server logins from SuperOffice
This is done by creating a user in SuperOffice with userid SA, give this user Userlevel 0 and the same password as SA has in the SQL database. Then when you log in as SA in SuperOffice, you can manage both SuperOffice and SQL server users from the SuperOffice Maintenance menu. This method is recommended if the SQL Server login used by SuperOffice isn't used by any other applications on the SQL Server.

How to manage users in this way is described below in E.2

Warning:
If another user than SA with Userlevel 0 tries to manage users from within SuperOffice, the changes will be applied in SuperOffice but not on the SQL Server. This means that this user will be locked out of SuperOffice until SA solves this problem manually on the SQL Server or from SuperOffice Maintenance.

If another SuperOffice user with Userlevel 0 than SA is going to manage Userdefined Tables in SuperOffice, this users login on the SQL Server must have an alias to user SO. This is done by the following procedure:

  1. Run SQL Enterprise on SQL Server
  2. Log in as the SA user
  3. Choose Manage menu, Logins submenu
  4. Get focus on the user you just created from within SuperOffice.
  5. Modify his login information for the SuperOffice database. Set Alias = SO. Which group the user belongs to does not have any effect. The alias rights give this user enough rights to be a user level 0 user for SuperOffice.

E.1 How to manually create a new user:

  1. Log into the SQL Enterprise Manager as the SA user.
  2. Choose Manage menu, Logins submenu.
  3. Add a new login and give it access to the SuperOffice database by checking the Permit column.
  4. If this is going to be a user with userlevel 0 in SuperOffice you must give it enough rights by setting the column Alias to value SO.
  5. If this is going to be a user level 1 to 5 user in SuperOffice you must place the user in the SOUSER group.
  6. Log on to SuperOffice with a user with user level 0 rights.
  7. Define a new SuperOffice user by using the Maintenance menu and the Employees submenu. Use the same login id and password as when you created the login account on the SQL Server.

E.2 How to create a user from within SuperOffice when logged in as SA:

  1. Create a user called System Administrator in SuperOffice. This user will have a login id like SA. Password must be the same as for the SA user in SQL Server.
  2. Create a new user as usual in SuperOffice by using the Employees submenu on the Maintenance menu.

á