Difference between revisions of "CEM Intelligence"
m |
|||
| Line 17: | Line 17: | ||
* There is no group hierarchy among the groups granting access to modules, a user must therefore be added to the modules access group in order to get access. | * There is no group hierarchy among the groups granting access to modules, a user must therefore be added to the modules access group in order to get access. | ||
| − | === Modules === | + | === Modules === |
| + | |||
[[CEM Bank Intelligence]] | [[CEM Bank Intelligence]] | ||
| − | [[CEM Konjunktur Inteligence]] | + | |
| + | [[CEM Konjunktur Inteligence]] | ||
[[Category:Production_guidelines]] | [[Category:Production_guidelines]] | ||
Revision as of 08:45, 17 November 2009
Contents
CEM Intelligence
Solution resources and structure
Resource access
Rules for group access
Based on a few notes written so far about the group hierarchy:
- We have one group per module such as:
- CEM Konjunktur
- CEM Bank
- When several users from the same company are granted access to a module, then a group is created for that company and it is build into the group granting access to the module.
- Individual users are added directly to the group granting access to the module.
- There is no group hierarchy among the groups granting access to modules, a user must therefore be added to the modules access group in order to get access.
