Following you will find information which elements and attributes are "required", "optional", "not-allowed" or will be "discarded" in the input XML-stream when creating or updating such an object. In "create" the rule for creating a new object is defined. In "update" the rule for updating an object is defined. Possible values are: required | optional | not-allowed | discarded required: this element or attribute has to be delivered optional: this element or attribute can be delivered and will be kept not-allowed: this element or attribute is not allowed in delivery and will cause an exception discarded: this element or attribute can be delivered but will not be used required required required required discarded discarded discarded discarded discarded discarded optional optional required required required required discarded (see note 1.) discarded (see note 1.) 1. A created user account is always active. It is not possible to activate or deactivate a user account using the update method. This can only be done by using the activate() and deactivate() methods. discarded (see note 1.) discarded (see note 1.) 1. Currently, the person resource does not exist and this element is ignored. optional optional (see note 2.) 2. If this element is not provided during update, all organizational-units are removed from the user account. discarded discarded discarded discarded discarded discarded discarded discarded discarded discarded discarded discarded (see note 3.) 3. This attribute is contained if the resources element is retrieved as a sub resource. It is not contained in the resources element within the user-account element. discarded discarded (see note 4.) 4. This attribute is contained if the resources element is retrieved as a sub resource. It is not contained in the resources element within the user-account element.