| This manual is deprecated. Please visit https://groupoffice.readthedocs.io for the latest documentation. |
Difference between revisions of "Getting started"
From Group-Office Groupware and CRM Documentation
(New page: When you've got everything working properly a very important step needs to be taken. The setup of the Group-Office environment. This page will give you an example of what we think is the p...) |
|||
| Line 9: | Line 9: | ||
# Installing/removing modules | # Installing/removing modules | ||
# Creating items that are commonly used for more users such as a global addressbook, shared calendars or a corporate HTML template for outgoing e-mail messages. | # Creating items that are commonly used for more users such as a global addressbook, shared calendars or a corporate HTML template for outgoing e-mail messages. | ||
| − | It's very important that you do this as an administrator so you will avoid the following scenario: | + | #;It's very important that you do this as an administrator so you will avoid the following scenario: |
| − | User 1 creates an addressbook and projects. This user shares these items with everybody. Everybody uses those items. Now User 1 no longer works at your company. Time to remove the user account. Oops! The projects and his addressbook are gone too! | + | #;User 1 creates an addressbook and projects. This user shares these items with everybody. Everybody uses those items. Now User 1 no longer works at your company. Time to remove the user account. Oops! The #;projects and his addressbook are gone too! |
Revision as of 12:52, 14 October 2008
When you've got everything working properly a very important step needs to be taken. The setup of the Group-Office environment. This page will give you an example of what we think is the perfect Group-Office setup for companies that want to take full advantage of all Group-Office features for office use. The administrator account
It's important that you use this account only for administrative purposes. We strongly advise you not to use this account as a regular user for safety and usability reasons. Basically use the administrator account only for:
- Adding and editing user accounts
- Adding and editing user groups
- Installing/removing modules
- Creating items that are commonly used for more users such as a global addressbook, shared calendars or a corporate HTML template for outgoing e-mail messages.
- It's very important that you do this as an administrator so you will avoid the following scenario
- User 1 creates an addressbook and projects. This user shares these items with everybody. Everybody uses those items. Now User 1 no longer works at your company. Time to remove the user account. Oops! The #;projects and his addressbook are gone too!
