If an employee is in several departments, he receives the sum of the access rights. Consider the department as a role or group to manage your permission structures.
If you create a department, you should briefly describe the intended use under Note. You can also use departments in the workflow and at the latest then it is good to know what this means for the members.
In addition to the name of the department, you can control whether this appears in the employee selection dialog. The ToDo Team View allows all members of this department to look each other in the ToDo's.
The group mailbox is a way to put things on a ToDo list. So no one directly receives the relevant operations but can open them via Team ToDo. Here one would e.g. to save an invoice to process it mainly via the open item list.
Task Processor: Creation of new processes and participation in their processing
Working time recording: Presence: comes, goes, breaks
Goods issue: Create partial deliveries
Cash Register: Recording cash transactions
Bank: View bank statements and debit invoices
Contact Manager: Maintain contact information
Product Manager: Maintenance of product data
Inventory Management: Warehouse Management
Procurement: processing orders at suppliers
Goods receipt: Confirm goods receipts
Production: Control of production orders
Maintenance: management of equipment and planning of maintenance
Service Entry: Material & Time
Project staff: time recording, travel expense accounting, project assignment resource and budget allocation
Administrator - Organization: Maintenance of users and authorizations
Administrator client: Creation of employees, authorizations and process - relevant master data
Recurring operation: establishment of e.g. Bills repeats for a rent
Business Settings: Business Transactions, Terms of Payment, Terms of Delivery, Groups
Administrator - Operations: Business Transactions, Deleting Delivered Items, ...
Business Process Design: Design: Forms, Workflow, Reports
Send E-Mail: Can send e-mails
Reports: allows to create reports
Head: The head of this department has the right, e.g. To access resource planning directly to the members of this organizational unit. Others would only be able to dial the organizational unit.
higher-level: The higher-level organizational unit receives relevance in the process definition. This depends on the respective process design.
Forwarding rule for incoming e-mail. These can be sent directly to the members (the addresses are green and always starts with "m ...") This is your client's name, which you can use for your e-mail system.
The system knows "owners, editors and readers". Members of this department create tasks and contacts, and so on. These "objects" receive corresponding mappings. An owner may e.g. delete a task. An editor will change and a reader will only find it.
You can save a selection for contact creation that allows you to save different contact groups and properties directly. In sales, interested parties can be created, in accounting customers, suppliers in purchasing. You can organize that relatively easily.
The storage for a contact group can start a workflow. The events in the creation of a contact can be controlled extensively. This way we ease the workload for the individual and he does not have to think about initiating certain things to a new prospective customer, etc. (see events that can start a workflow form "new contact, updated contact ...")
The overview shows the roles and also e.g. This is a selection for "Create contacts" is deposited.
Just as for contacts, you can also make a selection for the product line for products.