Announcement

Collapse
No announcement yet.

understanding acces-combination-name

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • kniggisiggi
    replied
    thank u for ur reply.

    i thought so too, but got confused by the manual.

    Leave a comment:


  • Martin Heiland
    replied
    Hi,

    sorry if i don't get your problem wrong. The documentation suggests to have a standard permission set at a context. This avoids logical issues like "user a can invite user b to an appointment but user b does not have a calendar" and so on. It does not mean that it's not possible to have mixed contexts but we don't really like those because the user may struggle with some inconsistencies.

    Greetings

    Leave a comment:


  • kniggisiggi
    started a topic understanding acces-combination-name

    understanding acces-combination-name

    hello everyone,

    i am having some understanding problems with the provisioning-document.

    i set the access-combination-name webmail+ for context 1.

    now i set for user1 out of context 1 "--access-calendar on" by using the changeuser-tool!

    user1 can now use the calendar too. in the provision-document on page 13 (user management) it says: "..., all users in one context need to have the same access rights."

    later on it is saying the same thing with access-combination-name.

    i changed "--access-combination-name all" for user1 in context1 (still webmail+). and it works too!

    i am confused.....

    greetings to all

    kniggisiggi
    Last edited by kniggisiggi; 08-06-2009, 01:13 PM.
Working...
X