|
If you would rather set up the team manually, using the Team Administration command instead of the Team Setup Wizard, follow these instructions after creating your personal agenda and joining the team.
1. Setting Passwords
To set Team Administration and Team Membership Passwords:
1. Open your personal agenda in TeamAgenda.
2. Choose Team Administration from the Context menu.
This command is active only when you are connected to the TeamAgenda server. Once a team has been configured, a password may be required to access the Team Administration window. No default password is defined, however, so the first time you are asked for the password, simply click the OK button. This will display the Team Administration window.
As administrator you can now define one password that limits access to the Team Administration window, and another that limits team membership. Without the first password a user cannot make changes to the team configuration, and without the second a user cannot join the team at all. This can be used to prevent people from outside your team or company from making a remote connection to your team.
Note: A Team Membership Password must be defined if any users will be joining the team using TeamAgenda Web.
2. Defining Default Access Rights
To set users' default access to each other's agendas:
1. Choose Change Team Default Access from the list in TeamAgenda's Team Administration window and click Do it.
2. Choose the desired default access level and visibility in the dialog box.
The initial internal default setting permits all users to add to each other's agendas, in order to create meetings, and to see everyone's internal level commitments only.
(For a full explanation of TeamAgenda access rights, see "Access to Other Users" in the TeamAgenda online help.)
To set External Default Access:
With TeamAgenda Web, you can make your Team accessible through a web browser over the Internet.
The default access level for external guests connecting over the Internet is always set to "No Access", with a visibility level of "No Detail". This default cannot be changed. You must explicitly decide if a specific agenda or resource will be accessible to guests over the Internet (see the TeamAgenda online help).
3. Defining Resources
Resource agendas may be defined to schedule items such as meeting rooms, company vehicles, demonstration computers, large screens or other equipment.
To define a resource:
1. Choose Directory Maintenance from the list in the Team Administration window and click Do it.
2. Click the Add... button.
3. Choose Resource in the "What would you like to add" dialog.
4. Enter the resource name.
5. Click OK to save, or click New to save the resource and then add another one.
By default any user can add to a resource's schedule, and modify the items he or she has added). By default the resource is not accessible over the Internet. However, the administrator can define different default access levels for the resource if necessary:
To change the default access level for a resource:
1. Choose Access Maintenance from the list in the Team Administration window and click Do it.
2. Choose the resource for which you want to redefine the default access levels.
3. Change the internal default access by using the Default for internal users pop-up menus.
4. If the resource will be accessible over the Internet, choose the desired external access level and visibility from the Default for external guests pop-up menus.
4. Defining Public Agendas
Public agendas may be defined to schedule items such as group vacations, lunch breaks, car pools, courses, or special projects. Public Agendas are similar to Resources, except that the creator's name appears in front of the commitment title in the case of a synchronized commitment. Public agendas are defined in a similar fashion as resources; see above.
5. Defining Public Categories
Categories are used in TeamAgenda to classify commitments. For time-billing purposes, for example, every customer or major project could be a separate category, while, for confidential projects, specific categories may be made accessible to only some team members. You may assign each category a color.
To define a category:
1. Choose Public Category Maintenance from the list in the Team Administration window and click Do it.
2. Click the Add... button.
3. Enter the category name.
4. Enter a clear description.
5. Choose a color, if you wish.
By default, new public categories are entered in every user's list of personal categories. If the new category should NOT be added to each user's list of personal categories, uncheck the Include in Everyone's Personal Directory box.
6. Click OK to save, or click New to save the category and then add another one.
To restrict access to categories:
Public categories are normally accessible to all team members. If necessary, that access can be limited to certain team members only, for confidential projects, for example (see "Limiting Access to Public Categories" in the TeamAgenda online help).
6. Defining Holidays
Any user with authorization (see below) can add or change holidays as they would regular commitments. Use the Commitment Type pop-up menu in the Input window to define a working or a non-working holiday. Holidays appear automatically in all user and resource agendas, and are imported automatically into the personal agenda of anyone who joins the Team.
To import holidays:
1. Choose Team Administration... from the Context menu.
2. Choose Import from the list in the Team Administration window, then click Do It.
3. Locate the Holidays folder on the TeamAgenda CD-ROM or on your hard drive; open it and locate the holiday import document corresponding to your country.
4. Click OK.
The holidays will be imported.
Your team has now been set up. Further TA-Server options are explained on the TA-Server Options page. These include entering additional license numbers, configuring network protocols, and enabling e-mail, FirstClass and FileMaker Pro integration;
Click this link to continue to the TA-Server options page:
Setting Up TA-Server Options
Go back to:
Configuring TeamAgenda and its Components
|
