Authorising Team Members

When you created authorisation tables, the Create Tables options you ran has automatically granted yourself, as repository owner, access to the USoft Authorizer tool. You now need to use this tool set up access rights to USoft Developer for the other development team members.

As the owner, from the USoft Binder file, open the Authorizer item.

Team members play typical roles in a project. Think of developers, architects, analysts and administrators. USoft recommends that you assign each team member to one of more of such user groups and then specify authorization for each user group. Each project is different but to give you a quick start, USoft has pre-defined typical user groups for you, for which you can change or drop access rights later as required.

Run the Load Definer User Groups option from the Tools menu in the Authorizer if you want to use these pre-defined user groups. This is recommended.

Now register all database users you have created for the development team members. Then for each database user, specify that he or she has access to the USD application. This is the USoft Developer tool. You do this by specifying the database user as a member of one of the user groups of the USD application. The Authorizer has a New User Wizard which makes it easy for you to complete this task.

Access rights and membership of user groups can be changed at any time.

In addition to the USD application, development team members may also need to access other USoft applications used in your project, such as USoft BenchMark (default application name USTESTER).

Moreover, if you want development team members to use a central runtime application for testing and prototyping, they need access to this application as well. The default runtime application name is the name of the repository owner. (If the repository owner name starts with the "OPS$" prefix (Oracle) then the default application name does not have this prefix.) It is a good idea at this point to change the runtime application name to something meaningful to the organization. This is particularly important if the application is going to be run alongside other USoft applications in the production environment.

Finally, since developers log on to the RDBMS using their own database user name, each of them (except the repository owner) needs to be granted access to the repository tables at RDBMS level, too. Grant these RDBMS privileges by running the Update Application Rights tool in the Authorizer. Each time you extend access rights to new users, you need to re-run this utility.