The solution owner is responsible for creating the instance of a team solution on the server and for maintaining the solution once it is installed. This involves the following responsibilities:
The solution owner can create an instance of a team solution from a template using the New Team Solutions wizard. For more information about launching the wizard, see Accessing the Access Workflow Designer Tools.
The wizard makes it possible for you to select a template, specify the solution title, specify database and Web names, and add users to the solution database roles. Once the wizard is finished, a new solution database and Web site are registered, created on the server, and available for use.
For more information, see Creating a New Solution from a Template and Deleting a Team Solution from the Server.
Team templates store the information required to create an instance of a team solution. The template is similar to a snapshot of the solution database and Web site. You can use the Team Template wizard in the Access Workflow Designer to create a new team template based on an existing solution. Then, use the New Team Solutions wizard to create a solution from the template. For more information, see Managing Team Templates.
The user directory contains information about the users who are registered on the server. The User Information tab in the Team Solutions Manager contains a list of users who have access to the local SQL Server using the SQL Server login. This information is available for use in team solutions. The user information can be manually entered by an administrator or synchronized from Exchange Server. For more information, see Managing Users and Roles.
A solution owner must have permissions to create new solutions on the server, to create and modify SQL Server databases, and to create and modify Microsoft FrontPageŽ Web projects on the server. The server owner is responsible for granting the appropriate permissions to solution owners. For information about user permissions, see Creating Accounts, Logins, Roles and Users.